“Please click here to refresh the preview.”
-
With the latest update, after adding images to Meow Gallery, the backend states “Please click here to refresh the preview.” instead of showing the images. Using Gutenberg editor.
Meow Gallery has been pretty buggy lately, I’ve got to say …
- This topic was modified 3 years, 2 months ago by bryanesler.
-
I have the same issue, “Please click here to refresh the preview.” Have you found any fixes?
Just downgraded to the previous version for now.
Same here with pro version.
Hi guys,
I am trying to replicate the issue, but can’t find a way. How are you using the plugin exactly? Are you trying to add images manually? Which method are you using?
Can you access the Settings of the Gallery? I am talking about the ones which are under the Meow Apps menu.
Currently, only the users with the role “upload_files” can access the Gallery Block. Are the users actually editors/admins? Maybe that could be that (the security of the plugin has been enhanced tremendously – and that might have an impact and we might need to review this all together).
Also, it would be good if you could mention what you see in the Console of the Developer Tools (Chrome) and your PHP Error Logs.
Thanks ??
Sorry guys, can you please try the latest version? Released just now: 4.2.1.
Thanks for the fix Jordy!
Sorry for this, and don’t hesitate to leave a little review if you feel like it, haha ??
Because I was having the issue at the sane time my host’s support staff changed and were useless in dealing with a concurrent issue (which they say was a DDOS attack), I decided to leave them. My prospective new host (MDD) said they were curious what the problem was with this Please Refresh issue and if it affected all users.
- This reply was modified 3 years, 2 months ago by tokyoprogressive5.
Writing to you from rainy Shinjuku! ??
My prospective new host (MDD) said they were curious what the problem was with this Please Refresh issue and if it affected all users.
There was a security issue with the previous versions of the plugin. Basically, as soon as you were authenticated (so you had to be registered to that WordPress install), by knowing the API perfectly and how to use it (by looking at the code basically), you could update options which didn’t belong to the plugin. That was mainly the issue. It never happened, but on a huge website with many thousands of writers for example, if one of the writer is a coder and looking for ways to break the site, that could have been possible. I don’t see it really happening, but everything possible ??
Anyway, it’s better to have a perfectly safe plugin, that’s a priority.
Thanks, Jordy. Do even though it never happened, why did the refresh thing happen?
Same in pro version, right!
Paul in cloudy Fukuoka.
Thanks, Jordy. Do even though it never happened, why did the refresh thing happen?
Haha, that’s true, I didn’t reply to the question ?? That’s simply because I increased the security a lot in the REST requests, with additional checks, and I forgot to pass a certain cookie holding the auth to the endpoint handling the previews.
Ok, I had my error log looked at by a coder.
And the fix mentioned on the forum did not work or work completely. For example, when trying to choose one of the gallery styles which has worked until now (carousel) I got this error in Chrome although this time the gallery was usable.
This is what he said.Not sure how much it relates to this plugin but this is what showed up after my error.
I should also note that I will be changing hosts next week to see if these problems remain.
deprecated.min.js?ver=932d8bb37da8bbb396a7a3f754345e08:2 Using Toolbar without label prop is deprecated since version 5.6. Please use ToolbarGroup component instead. See: https://developer.www.ads-software.com/bloc...nents/toolbar/ i @ deprecated.min.js?ver=932d8bb37da8bbb396a7a3f754345e08:2 deprecated.min.js?ver=932d8bb37da8bbb396a7a3f754345e08:2 Using custom components as toolbar controls is deprecated since version 5.6. Please use ToolbarItem, ToolbarButton or ToolbarDropdownMenu components instead. See: https://developer.www.ads-software.com/bloc...-blockcontrols
“These errors show that a plugin is using code that stopped working since a WordPress update from December 2020.”
i @ deprecated.min.js?ver=932d8bb37da8bbb396a7a3f754345e08:2
DevTools failed to load source map: Could not load content for https://www.paularenson.org/wp-conte…sheet.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE“This error suggests that theme is still using the code in a way that stopped working, and now the web browser is not able to the proper location of the css stylesheet.”
“Those errors would need to be addressed first, and then assess if the host is the issue.“A small amount of hosts will have rules in places of plugins clients cannot use. In some case I do agree since some plugins create more issues than most realize, but some on their list are a bit over-ruling. The odd time if a browser shows an error of not finding a code, there may be a security function in place from either the host or a plugin that’s blocking the code. Some developers will write lazy codes that will allow anyone access to your website, but in this case were dealing with outdated codes, which in some cases can also be a security issue…but that’s not meant to put fear into the equation. People who like to attack old codes will use scanners that will go through a website within seconds to see if it’s using old codes, or old plugins or themes. If a website matches what they have on their list, that person or bot will then attack that code as their way in. The “fun” side of WordPress that clients shouldn’t have to deal it, but is needed to make everything work as it should”
Note I am using the Pro version but comments here seem more frequent. I will take a rest until I can get on the new host who, using secure VPS, recommends that i stop using some of the WordPress Security programs.
- The topic ‘“Please click here to refresh the preview.”’ is closed to new replies.