Front-end editing issue after new update?

Hi @robertkun

I’ve tested several times WPBakery v6.4.0 and until now I had no issues working with the frontend editor.

In the other thread you mentioned this doesn’t happen always, but sometimes it works, right?

If it’s so, it could be a problem related to the maximum allowed PHP memory limit.
I suspect WPBakery and SCFM have some problems during the saving process when you use the frontend editor. In my case, I think I have no problems because in my installation the PHP memory doesn’t reach the limit, but probably in your installation, you are already near the limit and sometimes you reach it and the PHP parser stops the execution for fatal error.

These are just suppositions, let’s check if they could be the cause.

I suggest you do the following:

– oopen the file wp-config.php
– add these lines of code:

define(‘WP_DEBUG’, true);
define( ‘WP_DEBUG_LOG’, true );
define(‘WP_DEBUG_DISPLAY’, false );

Then use the frontend editor, and as soon as you have the problem check in the folder wp-content/ and tell me if you see the file debug.log and what you see inside that file if you see something.

Let’s also check if it’s a problem caused by a JavaScript conflict. When you have the problem on the frontend editor, inspect elements (F12) and click on “Console”. If you see red errors, please add a screenshot of the console.

Hi @robertkun
I think I’ve found the solution. Can you try the beta version 0.1.5?

Excluding a couple of lines of code, it’s the same as 0.1.4, so you should not risk.

You can download it with this link: https://downloads.www.ads-software.com/plugin/specific-content-for-mobile.0.1.5.zip

If the direct link doesn’t work, go to https://www.ads-software.com/plugins/specific-content-for-mobile/advanced/, scroll down until “Please select a specific version to download.”, select 0.1.5 and click on “Download”.

Then you should extract the zip and update the plugin via FTP.

Let me know if it solves the problem you have with the front-end editor of WPBakery.

Goodmorning Jose!

I updated the version to 0.1.5. So far so good! I opened a previous problematic page a couple of times with WP Bakery, no issues found.

I will update you asap if any issues arise.

Hi @robertkun

thank you very much for the information.

Never say never, but I think it will not happen again. I’ve tested it many times ?? on different installations.

In any case, if you have issues, let me know.

Jose I do occasionally get a internal server error 500, stating:

19.10.2020 20:16:50 forexdaytrader.nl [client xx.xx.xxx.x] FastCGI: “/home/strato/http/fastcgi/rid/50/28/510455028/htdocs/WordPress_SecureMode_03/index.php” aborted: incomplete headers (0 bytes) received from server after 8 sec

This could mean anything, but it just so happens they only show up on mobile versions of a page. https://forexdaytrader.nl/robotten/ is the example here again. Sometimes it works, sometimes it doesnt.

Perhaps its not related to your plugin but just throwing it in here anyway. Maybe you have a clue if something within the new version update could cause this.

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

Hi @robertkun

if you have noticed this issue also with version 0.1.4 the probability it has something to do with SCFM is not zero. But if you have noticed this issue since 0.1.5, I would say the probability that it’s caused by the version 0.1.5 is practically zero.

When you have occasional problems on the same page, and nothing else changes, and it’s not related to the cache, many times depends on the PHP memory limit or maximum execution time exceeded.

Probably SCFM gives its contribution to stress the server on a mobile page. The system is probably near the limits, and when it goes over the limits you have a server error.

Do you have many plugins?

If so, if you want you can disable the unused plugins on the mobile pages with Freesoul Deactivate Plugins.
Many plugins make run its code on every page, even when you don’t need those plugins. If you keep active only what you really need, the load on the server will be lighter, and you will probably not have anymore that problem.

Another test you can do, it’s going back to version 0.1.3 for a couple of days and see if you have again this issue.
Version 0.1.4 on the frontend adds some code on mobile pages compared with 0.1.3, but version 0.1.5, for solving the problem with WPBakery adds practically nothing compared with 0.1.4.

Hi @giuse Jose,

I love your plugin and use it on all my websites.

However, today when I was editing one in Elementor, I experienced a similar problem to what Robert has mentioned – Elementor gives the message “The content area was not found”. This does not happen on any other pages, just the mobile ones. When I enable Elementor safe mode I can access and edit the mobile pages, but my menus disappear and I can’t add them again.

I am hoping there is an easy fix / update for this? Your help and advice will be greatly appreciated.

(PS I have cleared cashe on all browsers, still happens).

Thank you

Hi @chrismartins86, thank you very much!

Version 0.1.5 fixes also this issue, I’ve tested right now with Elementor.

Have you tried it?

You can download it with this link: https://downloads.www.ads-software.com/plugin/specific-content-for-mobile.0.1.5.zip

If the direct link doesn’t work, go to https://www.ads-software.com/plugins/specific-content-for-mobile/advanced/, scroll down until “Please select a specific version to download.”, select 0.1.5 and click on “Download”.

Then you should extract the zip and update the plugin via FTP.

In any case, soon I will publish it and you can update the plugin as usual.
So, if you prefer it, you can wait until 0.1.5 is public.

Hi @chrismartins86
Version 0.1.5 is now public. You can update the plugin as usual. Let me know if you still have problems with the Elementor frontend editor.

@giuse Jose, you are a legend! The new update seems to have solved the issue. Thanks so much. Your time and skill is much appreciated!

HI @chrismartins86. You are welcome! Thank you very much for your nice words.

Hey Jose, i have been trying to find the cause of that error last days. I indeed dont think its related to your plugin. It might have been caused by a .htaccess file that got corrupted by an unknown cause. I removed and created this file again, so far no problems. But i have to keep checking

Hi @robertkun
thank you very much for the information. If you find any problem related to SCFM let me know.