djlaserman

I’m sorry to hear that @ibscape, I tried to highlight this TFCache issue to the Themify developers but even after several updates, this issue still stands, probably because no one has looked into it with any seriousness. The only fix unfortunately is to start building your website from scratch.

If you’ll use this builder, never disable it no-matter what, because if you do that your website will crash and you’ll not be able to re-enable the builder plugin

• This reply was modified 4 years, 5 months ago by djlaserman.

Where I used it is irrelevant @warengonzaga, if something is broken it’s useless, no need for sugar coating. Godaddy must pull up their socks and get their act together. To answer your question, I did that because I wanted to use the plugin to keep tabs on a staging site under a product that they sell for resellers for hosting, and that’s the only available way to do it for a stage site (currently), even though the production site may have other ways of installing it with some of their “managed WordPress” tools

I managed to debug the backend not showing issue to WP Total Cache remnants that had created several .htaccess files. jqmigrate was blocking four of the builder’s js scripts, I also had to remove most plugins as well as Autoptimize and the skin’s default required builders. I went further into the database and deleted all unused tables left behind by removed plugins.

Should you want to test the TFCache not found issue it is fairly easy to replicate. All you need is a fresh installation of wordpress, the javelin and javelin-child theme (with the javelin child theme active), then install themify builder. When that is done, disable the themify builder and try to re-enable it. Enjoy debugging from there on.

Your plugin definitely doesn’t play well together with caching plugins, clearing the cache several times just ends up corrupting the layout, the CSS would make the items look properly placed in the frontend but missaligned with (no CSS) in live view. To replicate the later, swap between the javelin child to javelin theme, then back to javelin child theme when there’s already page content done with themify, the content will lose it’s CSS and would need to be redone from scratch. I saw this when I had created rows with logos sized min height and max height to 100px and the logo images no larger than 98px in size, then swap the themes and re-swap as was and test the live view versus the frontend view. You should see that the CSS would show things correctly while inside the builder’s frontend but missplaced in the live site. Also as soon as you install themify, add linked APIs for google maps and bing maps and save the settings. after the experiments above go check on the APIs, you’ll find them blank again.

Should I get further quirks I’ll definitely email you our site info with a temp admin profile for you to investigate. Otherwise my OCD wouldn’t let me use other page builder plugins which I’ve tried before incl. (elementor, beaver and divi | which I don’t like because they are not as intuitive and clear (aka: design of everyday things) in usage and some are way too computing resource heavy).

The last tip or hint I’d give out to you, do include a form builder as part of your plugin, one that is customizable including things like the height and width of the text boxes, phone field patterns, drop down menus, google captcha, appearance CSS stuff like color, alpha etc. and do add more stylish templates than what’s been there since last year or so.

• This reply was modified 4 years, 9 months ago by djlaserman.
• This reply was modified 4 years, 9 months ago by djlaserman.
• This reply was modified 4 years, 9 months ago by djlaserman.
• This reply was modified 4 years, 9 months ago by djlaserman. Reason: Spelling mistakes and forgotten details in content

Yes I am working on the site as we speak. There are quite a few other quirks with the plugin like forgetting the Linked APIs so sometimes things like google maps would stop working.