Conflicts with WP to Twitter

Sometimes other plugins can cause conflicts with the calendar. When this error happens there is often a more detailed error in the console of your browser debug tools. Can you please look for that error add it here. Thank you.

Here is what comes up in the console.

There was an error contacting your blog.
edit.php:1200:365
showError
https://www.XXXXX.com/blog/wp-admin/edit.php:1200:365
error
https://www.XXXXX.com/blog/wp-admin/edit.php:1191:452
i
https://www.XXXXX.com/blog/wp-admin/load-scripts.php:2:27444
fireWith
https://www.XXXXX.com/blog/wp-admin/load-scripts.php:2:28213
y
https://www.XXXXX.com/blog/wp-admin/load-scripts.php:4:22744
c
https://www.XXXXX.com/blog/wp-admin/load-scripts.php:4:26925

Is there any chance I can access your blog and see this myself? You could send me login credentials at [email protected]

Sure. Thanks. You should have an email.

Thank you for sending me a login. I just tried this and everything is working. Did you make a change or do something else to fix this?

I had deactivated WP to Twitter so I could use the calendar. I have it activated again and the calendar is throwing the error again if you want to log back in.

This looks like the WP to Twitter plugin is overriding one of the get posts functions that the calendar depends on. This happens when other plugins try to inject HTML into the posts stream since the calendar uses that to generate JSON data.

There’s not much I can do about this on the calendar side. You would have to ask the WP to Twitter plugin developers to take a look.

Are you referring to the get_posts function, itself? WP to Twitter makes very little use of that function, and only in Pro; what is the conflict you’re seeing? I’m not sure how WP to Twitter would be injecting anything into the posts stream.

Honestly, it was just a guess based on trouble we’ve had with other plugins in the past. I would need to set this up locally and do some more debugging to see what’s going on.

Solved. It ended up being a memory limit issue. I noticed an admin page load was clocking in at 42mb and therefore over the standard wp limit of 40. Once I set define( ‘WP_MEMORY_LIMIT’, ‘256M’ ); my problem when away. Now to find out what is the memory hog…

• This reply was modified 6 years, 6 months ago by ImprintEd.