doffine

Hello @awelzel,

we just updated to v2.53 – all is fine now! Thanks a lot for your quick work!

Hello @awelzel,

thanks for your quick and detailed reply. We perfectly understand all what you said. We are looking forward to the fix and will rollback to 2.10 meanwhile.

Thanks again for your work!

Hey guys, please install a fresh copy and hopefully it will be solved.

Cheers!

Problem still exists. Just tried.

Use the previous version PageBuilder

We already did this just to be able to make changes in the old widgets. But this cannot be a solution forever. In Germany we have a saying for sth. like this, it means: “The tail (SiteOrigin Widgets by CodeLights) is fawning with the dog (Page Builder by SiteOrigin).”

I like the flipboxes, do you know a replacement?

That is exact the same thought and question I have, too. Perhaps someone here can give us a hint?

Same problem here. We ask ourselves whether to replace this plugin or if it still makes sense to hope for an update.
The fact that their website currently has an SSL error doesn’t look good, too…

Hello @wpmanageninja

we just updated all WordPresses to 3.2.2 and you’re right: Everything is fine now. Thank you very much for your very fast fixing and your nice mail! ??

-doffine

Mail is sent.

Where can I send you URLs privately?

Fixed in v2.2.7

The problem is solved for all of our installations. Many thanks!

@boazpojo,
I opened the issue on GitHub as requested. I just copied @techjewel’s initial text from above.

• This reply was modified 6 years, 4 months ago by doffine.
• This reply was modified 6 years, 4 months ago by doffine.

Hi @boaz,

unfortunately the new version 2.2.5 didn’t fix the problem :-(.

No matter if we use the little “X” in the top right of the nag window or if we use the “Hinweis ausblenden” (in German) button – the nag window is back the next time we load the dashboard front page.

Same problem here in several installations…

Hi Arno,

perfect – now it works without any additional ps. Thanks for your quick fix!

Hello Arno,

well, this is perfect! Thank you for your versed reply… we are looking forward to the update. Until then we just passivated the p via additional CSS “display: inline”.

Thanks again and many greetings!