Slow editing

[lbdesign]

I’m working with the demo content for Uplift. In making modifications to the sample home page layouts, I find that loading the Swift editor, making changes and saving pages takes a LONG time. Like, I can get up and make tea. Not like 3 seconds, but like more than a minute sometimes, (and it’s never fast). Even opening up one content element on the page to make changes can take to a count of 30 seconds. I have tried in both Safari and Chrome. My Macbook Pro has 16gig ram & pretty fast. Editing other themes is much faster. Is there an issue with Uplift, or the framework or the builder?

thank you

[Rui Guerreiro – SUPPORT]

Hi,

Something is wrong, my MBP also has 16BG Ram and it’s fast.
Try to disable all the plugins except Woocommerce and SwiftFramework.

Also try to open the javascript console to check if any error appears there.

-Rui

[lbdesign]

This reply has been marked as private.

[David Martin – Support]

From what I see when logged in, it’s working normally – is this still an issue for you?

What is a page URL you experience this on?

Thanks.

[lbdesign]

If you edit the Home page, you should see it load slowly, and save very slowly — like 60+ seconds to save the page.

Do you see that?

There appears to be damage to the database — perhaps from the demo content imports, which all took a long time and ultimately failed. When I make a virgin WP installation with just the theme and manually-created pages, it is faster.

[David Martin – Support]

Yes I do see that for the homepage, I have not seen anything that extreme before.

– I see no console JS errors.
– Can you ask your host about this error also, they should be able to see what process are specifically causing this.
– As I see it currently, it’s only that page. Is the correct for you also?

Thanks.

[lbdesign]

Thanks for looking at this. I agree the home page is the slowest. A simple page saves faster. I’m not sure if it’s because of multiple drafts of this home page, or the content of the page. And like I said, I suspect something went wrong with the demo content import.

I created a virgin installation of the Uplift site, with NO sample demo content, and it saves the home page in 15 seconds, rather than in 60 seconds.

I turned on error logging, and so far the only error I get is:

[28-Jul-2016 22:45:19 UTC] PHP Warning:  include() [<a href='function.include'>function.include</a>]: Failed opening '/home/learnfro/public_html/cam1/wp-content/advanced-cache.php' for inclusion (include_path='.:/usr/lib/php') in /home/learnfro/public_html/cam1/wp-settings.php on line 74

[David Martin – Support]

Hi,

What is the scope to copy that page into another test page no drafts / revisions?

I cannot do this as I cannot login:

I’ll ask my colleague Rui to take a look at this also and offer his advice.

Thanks.

[lbdesign]

This is interesting. With WP-Debug set to True, the site failed, and the following 3 error messages appeared. Do you know what they mean?

Warning: include(/home/learnfro/public_html/cam1/wp-content/advanced-cache.php) [function.include]: failed to open stream: No such file or directory in /home/learnfro/public_html/cam1/wp-settings.php on line 74

Warning: include() [function.include]: Failed opening '/home/learnfro/public_html/cam1/wp-content/advanced-cache.php' for inclusion (include_path='.:/usr/lib/php') in /home/learnfro/public_html/cam1/wp-settings.php on line 74

Warning: Cannot modify header information - headers already sent by (output started at /home/learnfro/public_html/cam1/wp-settings.php:74) in /home/learnfro/public_html/cam1/wp-includes/pluggable.php on line 1167

I turned debug off, and now you should be able to log in normally and experiment with page edit speeds, etc. Feel free to hack away at it. I will not continue to develop on that installation. I consider that installation “damaged” in some way. It would be great to find out how it got messed up though!

[lbdesign]

I’m also attaching the php error log. This is generated by the host’s cpanel.

Attachments:

You must be logged in to view attached files.

[David Martin – Support]

Hi,

All those error messages are related to the plugin Advanced Cache.

If you keep all the plugins disabled except for Woocommerce and SwiftFramework then re-test the debug on.

Thanks.