Tagdiv composer unusable

For some reason I am unable to edit posts or pages using the td composer. All green in theme status, using the version downloaded yesterday upon purchase, so the most recent, ditto wordpress.

If I click edit with td, I get a grey-white page with a permanently spinning spinner. Nothing else.

I can see plenty of other posts getting answered. Is there a reason this one isn’t?

Are you unable to edit anything or you can’t edit particular elements of page? You should be able to edit at least some stuff when using it!?

I get a whole screen white-grey page with a spinner. Not a single thing else. It cannot be closed either and needs the ‘back’ button to bale out.

Sorry but are you support for this theme?

This is scary; it looks like a user forum. I paid for a theme with support.
Where do I get it?

Hi, i have a similar trouble, it was solve updating the permalinks

look the tagdiv composer use some internal linkage to work

hope to help

best regards

They answer support queries in order received, oldest first, so reposting over and over pushes query further back.

Often problem with plugin is a conflict with something else… caching issue… or php version too old, etc. … lots of possible reasons. Not every server, hosting, or plugins used the same everywhere, hence why it works for 9 people but not the 10th.

Chris; I assumed newest posts would be read first, but watching other posts getting answered while mine got shuffled down to the second page without an answer persuades me otherwise. Sadly, there is no conflict, php7 is modern enough, i have a dozen wp sites on this server that run flawlessly and as this site is not yet what I call ‘ready’, it doesn’t even use caching.

One suggestion was made; that on the page that never finishes loading (any page opened with td-composer) that js was shown as not concatenated. It was said this ‘could’ cause issues. One assumes that if it ‘does’ cause issues it would already be known, but I have asked for advice from my hosts – luckily I have 4 vps accounts with them and they answer within the hour.

I have spoken to my hosting support team who say there is nothing wrong with the hosting and nothing missing. Given that I don’t have issues with other sites or plugins I can only agree.

I have, as requested, added the define( ‘CONCATENATE_SCRIPTS’, true ); to wp-config and as I said, it didn’t make any difference at all.

Can you please have a look and tell me what the issue is? The login details are still valid.

Can you say what the error message that shows up in console relates to, as it still exists now, after the change you specified.

We have switched from php7 to 7.1 and also 5.6 but that makes no difference. We totally deleted your plugin and reinstalled it, without making any difference. All that my hosting could say was that the problems, as they are, are only triggered when the edit with td-composer option is clicked. That would tend to suggest the problem is within the plugin. The error message points (also now after adding the line mentioned) to the same.

I’d really like to be able to carry on working on my site.

You may want to send your login credentials to tagdiv team to login and take a look.

I’ve been using it since it was in beta quite a long time back, and use it on my own server with CentOS/Plesk, with PHP5.6, 7.2 and zero issues.

There have been known issues with some plugins — when the plugin has an issue; like Yoast having errors, etc.

Turning on DEBUG MODE in WP can help; looking at error logs for domain, etc. all useful.

(FYI – point about old vs new posts getting answered; repeat posts on same thread make the thread ‘new’ again, vs ‘old’ and the non numerical way they answer stuff here means if you “leave it be” it will get answered quicker; if you keep posting updates, or others try to help; it actually gets answered LATER… but I don’t work here; just been on here since 2013.)

ALSO -worth noting if your host is using some kind of minification setup; that best to turn that off if it’s trying to rewrite javascript or CSS.

And, obviously, good to disable stuff like ad blockers or other shenanigans or extensions in Web browser ‘blocking’ page elements.

Right now I can’t share social items on Google News because Chrome’s own stupid popup blockers are blocking Google News from popping up share box (!!). *sigh*

Chris, are you tag div tech support? With 8000 posts, I guess you are that, or just marketing.

If you look at the emails sent to you weds, yesterday and today, you’ll find they include site logins, ftp logins and feedback from hosting, who spent a lot of time looking into this yesterday.

Fairly obvious catch-alls like disabling all plugins, removing and reinstalling td plugins, all that sort of stuff was done on wednesday. It was repeated by hosting yesterday, who took the time to also visit wponion.com to see what they could find there.

1. https://www.wpion.com/members/system-status/
>>>> The system status parameters guide given by ‘tagdiv’ support has been already configured on the server. The current PHP Handler set is fcgi, which can be changed to suphp (the default handler set for PHP 5.6 and PHP 5.5) is the only remaining configuration to be checked to check whether the error resolve or not.

(currently on php7)

2. https://www.wpion.com/members/topic/tagdiv-composer-not-working/
>>>>> TagDiv support states: You can try to disable all the plugins except tagdiv composer and check again.
(done on multiple occasions to no effect)

https://www.wpion.com/members/topic/tagdiv-composer-doesnt-work-anymore/
>>>> TagDiv fix in the forum: Usually recommend folks put the explicit https path for website and plugins folder into the wp-config.php file, while adjusting the amount of RAM allocated to WP.

(server has 5gb ram, php setup as below)
[PHP]
max_execution_time = 300
max_input_time = 600
max_input_vars = 5000
memory_limit = 128M
post_max_size = 8M
session.gc_maxlifetime = 1440
session.save_path = “/var/cpanel/php/sessions/ea-php70”
upload_max_filesize = 8M

https://www.wpion.com/members/topic/tagdiv-composer-not-working-3/
>>>> Same solutions mentioned above.

They pointed out that there is nothing else they can do or try, that none of my other wp sites have issues and that the error in any case only exists when a user tries to open td-composer.

Your own tech people have logged into the site twice today. I know they opened and tried to edit a couple of pages and looking also in my hosting files I can see they also accessed newspaper/includes/wp_booster/wp-admin/panel/td_view_system_status.php which I’m guessing gives them a rundown of the system, so they already know it is set up correctly.

The issue seems clearly related to td-composer. I’ve seen posts in various places about it, not just here, and it seems quite a few people have had and are having problems with td-composer not working for them. What I haven’t seen anywhere is a solution, which is very, very frustrating. I have been unable to continue working on my site for two whole days now.

As a fix has been found, and as it had nothing to do with hosting or other plugins, perhaps the advice I was given on how to avoid td-composer breaking (by not saving shortcodes until the next update) should be posted for people to see, and also what the temporary fix was? I can’t imagine I’m the only person to be affected by this.

Thanks to your tech support for finding the bug and fixing it.

Publish the fix, please. A similar problem, so I’m using WPBakery Page Builder. Or tell me how to disable the automatic inclusion of the tagDiv Composer after the theme update.

Perhaps it would be good if you could post the fix here? As it seems like there are loads of people with tanking websites because of this.

I myself is on the edge of switching theme completely (I own 2 licenses). Google is starting to punish my site because of these 500-errors that your theme is giving.

Could you please post the fix you gave Brian, here on the forum?

Thanks.