This happens to my site almost every single day! TagDiv Composer suddenly deactivates itself. After this happens only garbage is displayed on the home page (and any other pages created with tagDiv composer).
I didn’t change anything. I didn’t update anything. This just happend from nowhere.
Sometimes it is ok for a cople of days. Then all of a sudden it deactives itself.

I would like to know the root cause of this.
Of course you can say “update everything”, which every software vendor will say if you ever encrounter a problem.
But I am wondering why this happens, if I didn’t change anything

Hi Calin,

Now it works.
As you recommended I have updated to PHP 7
and then added the line SubstituteMaxLineLength 10M to the mod_substitute.c-section in the .htaccess file

This solved the issue.

Thank you very much!

Regards
Stefan

Hi Calin,

This is a very generic reply which could fit almost any question.

As I said: It was working perfectly before. I didn’t change anything since then:
No WordPress update, no theme update, no plugin installed, no manual code change, nothing. Not even a new page created. This is what worries me.
Of course, if I had changed anything since it worked, the first thing I would have done is undo what I changed. But I didn’t do anything. The TD composer simply stopped loading.

Here some additional info if it helps:
Theme version: 9.2.2
PHP version: 5.4.45
Wp version: 4.9.9

Have you ever seen this type of blank screen when launching the TD composer?
Is there any ‘debug mode’ or anything that would make the composer give more information about what is going on? I don’t get any error message.

Please try to help me. This is really serious. It is a live site and I cannot edit any of the pages although I didn’t chnage anything!

Now I was able to solve the issue on my own:
I just recreated the page from scratch. Now I will never know what the actual problem was, but what matters to me is that I now edit my page again 🙂

But again: My suggestion to the development team is to please improve the error messages. Errors can always happen (nobody is perfect) but if we get more explicit error messages it will be alot easier to track down and fix issues.

Yes, I know I can download, edit and create templates.
However, I still need the sidebar because I am including it in all my posts. I am not using the tagDiv PageBuilder for my posts because there are several 100 of them on my side. So I only use the regular editor and always have the same sidebar.

Bascially my question is: How do I create new widgets? Maybe from downloaded or edited templates? How do I get from a page template to a widget that can easily be included in a sidebar?

In my case it is not due to an updated theme, because I am still running 9.2.2
But I came across this page here: https://forum.tagdiv.com/tagdiv-composer-not-working/
There it says: “This error appears in the tagDiv Composer page builder screen when you are trying to edit a page that contains unsupported shortcodes. The most frequent cases are: the page was modified in the backend by adding code or scripts directly through the TinyMCE editor or if you’ve inserted HTML code with missing tags. ”

This is what I was thinking when I saw that error. The error message to me sounded like an inconsistecy of parsed data that doesn’t match an expected syntax.

Just that I don’t think I edited the content manually outside the Composer.

But just as a suggestion: If the Composer really encounters an unexpected element, then it would be helpful to have a message like ‘Illegal tag xyz found’ or ‘Parsing error at position 232’ or something that can help me track down the error.
Maybe you could consider that for future versions.

Hi Simion,

It worked!
Thank you very much

Stefan

I am getting a similar error always when I want to edit one particular page with the DivTag Page Builder! “Error at rows: 6(models) : 9(dom). The model does not match the content”
I have many pages on my site. But only this one page always throws this error when starting the DivTag PageBuilder.
The PageBuilder hangs when being invoked and displays this error on the top right corner.

So now I have a page that I cannot edit!!!
All other pages are fine.

I am using
Theme version 9.2.2
PHP version 5.4.45
Wordpress version 4.9.9

Stefan

Hi Simion,
Yes, I have noticed that flex blocks have that setting.
But I would prefer to set it just in one place – no matter which type of block I use. Using flex blocks in every single instance and having to configure it in each single flex block on each page individually would be a nightmare and is therefore not an option. I thought there must be a simple configuration I have just overlooked. If I have to use CSS then I will if you tell me where – but I guess that would mean changing the code of the theme and with a theme update it would probabaly be overwritten.

Do you at least have a simple solution for the breadcrumbs?

Regards
Stefan

• This reply was modified 7 years by StefanK.

Is there any other way to import the demos, like first uploading it to the server and then importing it somehow?
I guess most of the execution time is used by your script fetching all the images from your server within one call. This causes it to timeout.

I know that for example it is recommended to increase max_execution_time to over 60.
But I cannot change that. I am on a shared hosting account at Hostgator.

Here is what they say:
PHP Settings that Cannot be Changed

Shared packages (including Cloud Sites and Resellers) are hosted on carefully managed environments and have certain limits on what can be changed in order to maintain the stability of the server. Dedicated Server and VPS customers may change all the settings in the php.ini file and do not have the same limits as Shared and Reseller hosting.
Shared (Including Cloud Sites and Resellers)

PHP has been configured to use the following settings on our shared and reseller servers:

safe mode = Off (cannot adjust)
memory_limit = 256M (MAXIMUM)
max_execution_time = 30 (MAXIMUM in seconds)
max_input_time = 60 (MAXIMUM in seconds)
post_max_size = 64M (MAXIMUM)
upload_max_filesize = 64M (MAXIMUM)
enable_dl = Off (cannot adjust)

The above settings either CANNOT be changed or exceeded on Shared and Reseller accounts. These limits are set to prevent extremely high resource usage in shared environments. We have found that a majority of the PHP scripts will work within these limits, and the scripts that require more resources are best suited for a VPS or dedicated server.

• This reply was modified 7 years by StefanK.

Some more info in case you need it:
WP version: 5.0.3
PHP version: 5.4.45
Theme Version: 9.2.2

Post max size: 64M
max execution time: 30
max input vars: 1000