C5-8.1.0 - how to disable page review popup

Permalink
Hello,

Every time I load/reload a page on my site, a page Review popup (see attached) appears and shows me an empty Requested Version and a Live Version.

I don't understand the purpose and value of this thing. How can I disable it?

Thank you.

1 Attachment

linuxoid
 
MrKDilkington replied on at Permalink Reply
MrKDilkington
Hi linuxoid,

Is this a new install, existing install, or upgraded install of 8.1?

Are you running custom code?
linuxoid replied on at Permalink Reply
linuxoid
Hi,

It's a new install without content. Looks like it shows me for review 2 versions of the home page: the very first one after the install and the latest (live). What's the point if there's nothing I can choose or do about it? BTW, it only happens if I'm logged in.
ntisithoj replied on at Permalink Reply
ntisithoj
Did you ever get an answer to this? I have the same problem. No custom code... but a permission error in an attempt to publish. fixed the perm issue, but now get review popup :(
ntisithoj replied on at Permalink Reply
ntisithoj
putting this in index.php, or wherever, at least makes it disappear... at least until someone can tell us what it does an how to make it stop doing it.

<style>
.ui-pnotify .ui-pnotify-shadow {
 display:none;           
}
</style>
ntisithoj replied on at Permalink Reply
ntisithoj
I take that back... that just messes up a bunch of other stuff. ARGGH! What a nightmare!
jasteele12 replied on at Permalink Reply
jasteele12
Never seen the problem, but this temporary hack would need to go into either your theme CSS file, or maybe your (home?) page Header Extra Content.

Have you tried different browsers - I'm assuming you are pressing Publish on the page and not just Save...
ntisithoj replied on at Permalink Reply
ntisithoj
I put it in concrete/themes/concrete/main.css. So far, so good. No, it can't be the browser.
ntisithoj replied on at Permalink Reply
ntisithoj
Yes, I am publishing. This problem seems to appear when a publish get messed up during the publish, for example, in my case, when the permissions changed and the published failed, but it seems that some fails are not caught, to the publish thinks it was successful... or something like that
MrKDilkington replied on at Permalink Reply
MrKDilkington
@ntisithoj

What version of concrete5 are you using?

Are you able to list the steps to reproduce this?
JohntheFish replied on at Permalink Reply
JohntheFish
I have seen the same problem. When the core breaks during a page save/publish (as it can easily do at random times), you get left with multiple unapproved version popups that won't go away.

Fortunately, most of my work is on development test sites, so its not that big a problem to delete the page and create a new one, or even scrub the site and start with new content.

It happened once on a live site and I ended up hacking the database.

Since then, this job has been posted by @hissy that may solve your problem
https://gist.github.com/hissy/5ea2147516a90710919d...

The problem can't be that unusual if a developer felt the need to put work into that rather than hacking the database one-off.
ntisithoj replied on at Permalink Reply
ntisithoj
Here is one way I believe will replicate the problem.

1. Edit a page
2. change permissions of application/files to RO
3. press PUBLISH on edited page
you'll get an error
4. change application/files perm back to RW
5. reload page
MrKDilkington replied on at Permalink Reply
MrKDilkington
@ntisithoj

I wonder if changing permissions after a page is in edit mode, but before it has been published, is causing the issue.

Is there a reason for changing permissions while between "states"?
ntisithoj replied on at Permalink Reply
ntisithoj
no good reason. In my case, I had two identical installs, and I messed up the config on one, which I remembered just before I published, so I rsynced the application folder but did so as root, unknowingly. Then I published and got a permission error. Granted, this is a very rare circumstance, but I have received this before under more 'normal' circumstances, and in any case, it highlights the fact that there is no recovery if there it runs into a fatal error on publishing.

It may not be worth a fix, being such a rare occurrence, but I would be happy if anyone could share what needs to be manually tweaked in the database, such as what JohnTheFish did.
Gondwana replied on at Permalink Reply
Gondwana
Did you rsynch without also copying the database across? Doing so risks 'misalignments'. Some of the c5 config is in files; some (including permissions, I think) is in the database.

But hopefully I'm misunderstanding.
ntisithoj replied on at Permalink Reply
ntisithoj
I was only reading the active dir.