-
Posts
-
Hello,
I copied a page on my website and modified it. All seemed to work well last Friday, but when I came back to it on Monday, the background image in one of the colour sections that was shown in Preview was wrong. It was the image from the original page I had copied. The image is right in Advanced Layout Editor, and it is also right on the live web page. It is only when I look at the page via Preview that the wrong image is shown.I have cleared my browser cache and the server cache, but this hasn’t sorted the issue. Bluehost (the hosting company) have also done whatever they can. They say the issue is with Enfold. Can you help please? (I’m putting some links below for you to see the issue.)
Thank you.
Hey cultorum,
Please post us your login credentials (in the “private data” field), so we can take a look at the preview page.
- Install and activate ” Temporary Login Without Password “.
- Go to ” Users > Temporary Logins ” on the left-side menu.
- Click ” Create New “.
- Add the email address for the account ( you can use (Email address hidden if logged out) ), as well as the ” Role ” making that the highest possible and the expiry about four days
( to be sure that we have enough time to debug ). - Click ” Submit “.
- You’ll now have a temporary account. Please provide us here in the private section the URL, so we can login and help you out.
When your issue is fixed, you can always remove the plugin!
If you prefer to not use the plugin, you can manually create an admin user and post the login credentials in the “private data” field.Best regards,
NikkoHi,
Thanks for that. I’m seeing the same problem on my end, but I’m not sure what is causing the problem unfortunately. I see that you have published the page, so I’m not sure exactly why you need to use the Preview functionality? It’s safer to check on the actual published page in my opinion.
If you want to dig deeper into this problem, then you can activate debug mode and move all the shortcodes to a new page: https://kriesi.at/documentation/enfold/intro-to-advanced-layout-builder/#debug-mode
Best regards,
RikardHi Rikard,
The fact that I have published the page is really neither here nor there. I am working on the page and want to preview it in desktop/tablet/mobile mode to see what it looks like on those devices. (There were issues with leaving it in draft mode. Some of the Layout Builder functionality didn’t work, though I cannot remember any of the detail.)If you could offer something a bit more helpful, I’d appreciate it.
Thank you.
Jutta
Hi,
What happens if you select to use the Classic Editor in the main page of the theme options?
Best regards,
RikardHello Rikard,
Back from holiday and I’ve taken up the battle again. I followed your advice and activated debug mode. Strangely, the name of the image does not seem to appear in the HTML. It seems to be picked up form somewhere other than the shortcode for the page. I’ve got a small step further, but I really think there is an issue which is not within my control and needs your help.I started the page from scratch, recreating the page element by element. It seemed to go okay. The page is now showing the right image and I recreated all the other sections. All went fine until I got to the very bottom of the page. There should be a light grey bar here (#ebefeb), followed by a green bar (#093300); except the green color section persistently comes out in white. No matter what I do, I cannot change the colour. I have tried different colours, adding in some text, forcing the section to be a minimum height, inserted another column below, swapped the color sections round, etc., etc. None of the changes showed. I then realised that even text changes elsewhere on the page no longer appeared in preview. It looks as if something somewhere just runs out of capacity and after a while, changes are no longer carried through to preview. Preview just reuses an older version of the page.
The only way I can see the results of my editing is by publishing the page and reloading the actual, live page. That is in no way satisfactory!! Could you please help?
Thank you.
Jutta
Hello Rikard,
I removed and updated various plugins and switched to the classic editor and it now seems to be working. Not sure what fixed it, but long may it last!!!
JuttaHi,
Great, I’m glad that you got it working. Please let us know if you should need any further help on the topic, or if we can close it.
Best regards,
RikardHi,
The login token you previously posted is not working anymore. Please renew it, or post regular login details in private.
Best regards,
RikardHi,
Thanks for that. I checked the site in private, but the preview seems to be correct on my end. Could you post screenshots of what you are seeing on your end please? Also, does it make any difference if you use a different browser, or a private browser window?
About the PHP notices; they are not really error messages and shouldn’t cause any problems on your site. A PHP version update might remove them though. Could you try updating PHP to 8.0 or higher?
Best regards,
RikardHello Rikard,
With these apparently random issues, it’s getting hard to see the wood for the trees, so I have written up some notes that (as far as I remember) document the of events in chronological order. I hope this will give you a pointer to where the problems lie. Thanks for your help in advance!12 Aug 2022: Bought Enfold licence to install update. (Website was originally developed by contractors in 2020, but we didn’t have licence key, so repurchased this in order to be able to install Enfold updates.)
8 Sep 2022: Installed Conditional Menus plugin. Subsequently, created new page cemetery-gardening, based on PlantRecorder home page. (Conditional Menus: original SiteNav for all pages except for cemetery-gardening, which uses GardeningNav menu.)
13 (?) Sep 2022: Noticed issue with editing cemetery-gardening page. Although the correct image was shown in the Advanced Layout Editor, preview had reverted to the original image from the PlantRecorder home page. (I am certain the issue didn’t arise when I started editing the page.)
5 Oct 2022: Recreated cemetery-gardening page from scratch (again, based on PlantRecorder home page). Page is now showing the correct image. However, later in the day, editing changes (colour changes in colour section, text changes,…) stopped showing in preview. (They did still appear on the live page (cultorum.com/cemetery-gardening instead of https://cultorum.com/?page_id=1305&preview=true). Switching from Block Editor to Classic Editor seems to fix the problem.
(No further changes other than to Yoast SEO until 12 Oct.)
12 Oct 2022: Issues with both the cemetery-gardening page and the PlantRecorder home page when coming back to making page changes.
Several pages started showing an error message in the editor: “Avia Layout Builder. Notice: Undefined variable: permalink in /home3/cultorum/public_html/wp-content/themes/enfold/config-gutenberg/class-avia-gutenberg.php on line 1431.
Notice: Undefined variable: permalink in /home3/cultorum/public_html/wp-content/themes/enfold/config-gutenberg/class-avia-gutenberg.php on line 1431”.
Cemetery-gardening<: Viewing the page (through Advanced Layout Editor; page in draft mode), the page only shows a green bar and a grey bar. No text or images, despite the fact that all content is clearly visible in the editor. Switching from the Classic Editor back to the (original) Block Editor seems to fix the problem and all elements of the page display in preview. However, towards the end of the day, changes (e.g. text changes) stop displaying in preview. After publishing the page, the changes can be seen on the live page, cultorum.com/cemetery-gardening. However, they do not show in preview. (This is the situation now. See text about half-way down, “What we offer…”. The first column says “Grave maintenance” in the editor, but in preview, the previous text “Maintaining existing planting” is shown.)
PlantRecorder home page: The page has lost its menu and no longer fills the screen width. (Other pages, e.g. Configuration, still display correctly.) Looking at the page in the editor, there is a message at the top saying that there was an autosave file which was more recent than the page being viewed. Also “A duplicate of this post was made”. Restoring the autosave file appears to resolve the problem. This is somewhat bizarre, as I had not made any changes to this page. (I only viewed it for reference when developing the cemetery-gardening page.) I also have no idea who or what made “a duplicate post” of the page.Hello Rikard,
Thanks for the screenshot. In the editor, the text under one of the icons about half-way down says “Grave maintenance”, but in your image, it says “Maintaining existing planting”. That’s what I’m seeing, but it’s not right. It is the previous text, which I changed yesterday.I tried Google Chrome, just in case, but same result. I never use Chrome, so it’s not a cache issue; and, anyway, you’re finding the same.
Jutta
Hi,
Thanks for the update. What happens if you publish the page privately, or use the password functionality? Then you wouldn’t have to use the preview functionality at all.
The last warnings you posted are all from from plugins, none of them are theme related.
Do you have debug mode active in WordPress? If you post FTP login details in private, then we could check for you, and turn it off if you like. Note that what you are calling errors are not actual errors. They are warnings and notifications, and should not affect any functionality on your site.
Best regards,
RikardHi Jutta,
Thanks for the update. I can’t tell you exactly where the preview gets its data from unfortunately, but everything on a WordPress site is saved in the database, and I don’t think that the preview would get the data from a different place compared to if the page is published. I know this is not what you would like to hear, since the preview on your site is not working correctly, but it does work when the page is published. Unfortunately, I can’t explain this behaviour in detail, since I don’t know enough about how WordPress core actually works in this case. All I know is that I would personally never use the preview functionality, since I find it unreliable. It’s much “safer” and more reliable to actually publish the page privately, then keep a separate tab of the front end open, and simply update that once you have saved. If you would like a second opinion on this, then I would be happy to ask the rest of the moderator team to chime in as well.
Best regards,
RikardHi Jutta,
Thanks for the update. I can’t tell you exactly where the preview gets its data from unfortunately, but everything on a WordPress site is saved in the database, and I don’t think that the preview would get the data from a different place compared to if the page is published. I know this is not what you would like to hear, since the preview on your site is not working correctly, but it does work when the page is published. Unfortunately, I can’t explain this behaviour in detail, since I don’t know enough about how WordPress core actually works in this case. All I know is that I would personally never use the preview functionality, since I find it unreliable. It’s much “safer” and more reliable to actually publish the page privately, then keep a separate tab of the front end open, and simply update that once you have saved. If you would like a second opinion on this, then I would be happy to ask the rest of the moderator team to chime in as well.
Best regards,
RikardHello Rikard,
Any thoughts on my last pot? Why does the HTML not change when I change the text in the editor? And was there any resolution of this previous query: https://kriesi.at/support/topic/preview-shows-old-version-of-site/? I feel the problem is now sufficiently well defined to get to the bottom of it, but I do need help.Thanks very much.
Jutta
Hi Jutta,
Sorry for the late reply. I’ve brought this up for discussion internally, but there are no further suggestions from any of the other team members unfortunately. We could try to move all your code to a new page to see if that changes anything, but the login details you posted earlier are not working anymore, so I couldn’t do it for you right now.
The other thread that you linked to has no further information other than what is in the thread.
Best regards,
RikardHello Rikard,
I suspect you’re right that creating the page from scratch would resolve the issue. There’s probably some crud left over from the original page which I copied. Is there an easy way of doing this (other than writing down all the settings and then recreating the page)? I have refreshed your login. If you could produce a new “clean” page, that would be great. Could you make it an additional page and not delete the troublesome page for now?If that doesn’t work, then I think I will have to try reinstalling various things (theme? editor?), but that thought scares me!!
Thanks.
Jutta
Hi Jutta,
Thanks for the update. I’ve created a copy of the problem page for you, please see private.
I see that you are not running the latest version of the theme. Please try to configure the Envato market plugin, then update via that.
Best regards,
RikardThanks, Rikard. I think you’ve done what you can. I’ll run with that. Strange that you say we’re not running the latest version of the same. I remember going through the Envato market setup and enabling automatic updates. I see against the Envato Market plugin that automatic updates are enabled, and every time I check for Theme Updates, I get “No Updates available. You are running the latest version!”. Something obviously not right with the setup. I’ll have another look.
Hi Jutta,
I see that you are running the latest version now, and that you are logged into the Envato markets plugin :-)
Best regards,
RikardWent back to the website with the intention of replacing my page with your newly-created one, but realised it shows exactly the same strange behaviour. Text in code editor not the same as in Advanced Layout Editor, updates not showing in preview… Looks like I’ll just have to live with it. Not worth spending more time on it, but hopefully, one day, there will be an update to the theme/plugin/Wordpress/… that miraculously puts things right again. Thanks for your efforts, Rikard.
Hi,
Thanks for the update, and sorry for this situation. I would advise that you try to publish your page privately instead, and update the front end, instead of using the preview functionality.
We’ll keep this thread open in case you should need any further help on the topic.
Best regards,
Rikard
- You must be logged in to reply to this topic.