edward_plainview

You can add your wallet address, but it will be overwritten after each increase of the xpub.

And we suggest 0 to start, and change the gap length in your wallet to skip over the non-payments, so it detects all the payments in the end.

We’ve had too many people email us, angry, that they can’t see the money in their wallets only to find out about gap lengths afterwards.

Payments not being found is usually due to the customers not paying exactly the amount requested, for some reason or other.

MCC uses exact amounts to differentiate between customers.

To avoid having to expect exact amounts, use an HD wallet and allow for a payment tolerance %.

We have just released version 2.138 of MCC that fixed the Phanton pay problem.

For some reason they changed their API, so we had to update our code.

In the debug text you sent me, I saw that your image filenames are just numbers. Image filenames ending in numbers confuse WordPress. So image1.jpg and seaside-3.jpg are not good for WordPress, for example.

Try inserting new images, with more random filenames.

Otherwise, I didn’t see anything wrong with the text: the gutenberg images are found and the IDs replaced with the equivalent ID on the child site. It’s just the numbered images which are most probably the source of the problem.

That’s not the complete debug text.

The debug text is a long, long, long text that is either displayed in the browser or saved to file, depending on your Broadcast debugging settings.

That’s the long debug text I need you to send me to read through.

No response. Closing.

The random images are usually due to the image IDs not being the equivalent.

I am unable to say exactly what is wrong with seeing a Broadcast debug text of the post in question.

I need more information. Could you:

• if enabled, disable the Broadcast queue add-on
  
• enable Broadcast debug mode: Admin > Broadcast > Settings tab > Debugging subtab
• Enable debug + debug to browser and / or file
• Clear the debug file
  
• broadcast the post to one blog
• send me the debug text to read through

This will tell me what Broadcast is doing. My email address is [email protected]

Great. I’ll rename the add-on to reflect the new plugin name.

Tested with version 4.0.4 of Future.

This is not related to broadcast at all.

You just have to show the webhost that if you change the site name in the subdomain, it doesn’t change in the network admin as it should.

What you did sounds logical and it should have worked (in my mind).

Why it didn’t I don’t know.

This is something you’ll have to ask your webhost about.

Sounds about right, yes.

If it did not change on the network, then the subdomain is not connected to the network.

If you do not see the broadcast menu item on the subdomains, then it definitely sounds like you have an incorrectly installed network, with the subdomains installed as single installs.

You should not have to reinstall wp on the subdomains – that’s probably the problem. There should only be one wp install, and then same wp network install handles the subdomains as you create them in the network admin.

I’m not familiar with how Godaddy handles installs, but however it is done now, is incorrect.

Just do the opposite of what you’ve done so far and you should be fine. ??

Nothing changed at all or nothing changed in the network overview / broadcast list?

Another way to see if the subdomain is installed as a single install, is that the broadcast menu item does not exist on the subdomain.

Try enabling debug to file mode and broadcasting.

We do not care about the page post type.

It looks like you need to look over the Broadcast custom post type settings.

Admin > Broadcast > Settings tab > Post types subtab

Add “page” in there.

One post type per line, no commas or anything.

It almost sounds like the Broadcast data table (the one containing the link info) is missing its ID column.

The way to check for this is to visit

Admin > Broadcast > Maintenance Tab > Broadcast data check

And see if it complains about a missing ID column.

If the ID column is fine, then there is something else going on. A long broadcast debug text of the post in question emailed to [email protected] will tell me what is going on.