Archived topic
Random Border Added After Update
24 replies · Started by Alex on October 7, 2020
As described above :)
This is happening on every single website using GP, I've had to restore backups on all of them.
Hi Alex,
can you share a link to where i can see the issue?
Hi David,
I have since reverted the update, but I've just created a staging area for it. I've added it to the private information area here.
Odd - the CSS order seems to be a little jumbled.
Add this CSS to correct that:
.inside-article .entry-content {
margin-top: 0;
}
Thank you – I'll test that. Just wondering...since it happens on every site – is there a reason the CSS order is jumbled in this particular case?
Updating is definitely the only thing that changes before the issue occurs / after the issue is there.
Best,
Alex
Also adding that CSS breaks other areas of the site.
Hi Alex,
What version of GP Premium are you using? Can you try updating to the latest?
Hi Tom,
This issue occurs when updating to the latest version of GP → 3.0.0
It does not occur anymore when I roll back to version → 2.4.2
Best,
Alex
What about GP Premium, though? It looks like you're using an old version.
If you update to 1.12.1, you shouldn't have this issue.
Let me know :)
The GP Premium plugin does not appear to have an update available? :)
Best,
Alex
Something is up there - GP Premium is at 1.12.1, not 2.3.2.
Perhaps the version number was changed locally? If you change it back to something like 1.10.0, it will trigger the system to fetch the latest update.
That's odd :)
Just updated the version number in the plugin editor, this didn't trigger it to fetch a new update. I've just re-installed GP Premium by downloading it from the account area here and it still shows the same version number...
Best,
Alex
Just downloaded it from the account page and opened gp-premium.php, the version number is set to 1.12.1: https://www.screencast.com/t/Soui0p4R
What does it say in your gp-premium.php file?
Ah, I guess it took a moment. I just updated GP Premium and then the theme file and the issue doesn't seem to happen when it's done in that order :)
Thank you!
Best,
Alex