MrsJessicaSimpson

“We do not have a popup for beta program notification, there is a notice banner for it.”

semantics doesn’t address the issue.

Pressing the:- “If you press [X] in the banner in plugin page” doesn’t stop the notice banner from [displaying] .. {{yet}} again ..

FYI Only ..

From your rapid response on this matter, I’ve now closed this support ticket.

eaglejohn(@danielbenjamins)

It’s unfair to give a one-star review: for what is essentially a free plugin that works flawlessly.

Yes: 3.2 had an issue of not being able to dismiss the advert, but the latest does indeed dismiss it.

Yes: it’s an advert, but the author’s got to make some money somewhere, have you donated to it (??) I have, that said: limited donations are not enough to keep it going.

It’s one small popup, give the guy a break.

5 stars all the way!

Message to George, .. [plugin editor]

This was, (and is), an amazing plugin, but the additional popup (that can’t be permanently dismissed), is a major distraction.

Had a look at your PHP code, and the popup is definitely coming from your latest 3.2 update.

Hoping that you can rectify this horrid intrusion: the admin popup really is an annoying aspect that I could do without.

And yes: I know that you have to make a living, but this definitely ain’t the way to go about it.

Laters ..

Cheers POD people, installed the new Shield plugin and my site now runs again, ..

But! – It’s only a kludge, being as there’s now huge banner on the dashboard warning about this incompatible Monolog library version number, and with no fix being sorted out in the near future.

So, that means that it’s now a toss-up between ShieldPro and subscription PODS, .. (no contest) – I’ve installed Cerber as an alternative, and now don’t have any dashboard warnings floating about.

Laters chaps ..

BTW, the PODS team are aware of this issue.

https://www.ads-software.com/support/topic/fatal-error-monolog/#post-16529444

My tupence worth (for what it’s worth)

I’ve included this text on ShieldPro and these support pages.

Been digging after my crash report email came through, and that was after updating the plugin SheieldPro.

This is their latest version:
Ultimate WP Security Protection – Scans, 2FA, Firewall, SPAM, Activity Log, Security Admin, and so much more.
Version 17.0.9 | By Shield Security

After updating this plugin – my website crashed out with the dreaded white screen of death,
Renaming (wp-simple-firewall) to (old-wp-simple-firewall), ..
IT WORKS AGAIN.

(BUT)
From reading the crash report email .. its seems like it’s the PODS side that’s now causing new error.

Version 2.9.11.1 | By Pods Framework Team | View details
This plugin failed to load properly and is paused during recovery mode.

An error of type E_COMPILE_ERROR was caused in line 93 of the file /home2/b92couk/public_html/wp-content/plugins/pods/tribe-common/vendor/monolog/monolog/src/Monolog/Handler/FilterHandler.php. Error message: Declaration of Monolog\Handler\FilterHandler::isHandling(array $record) must be compatible with Monolog\Handler\AbstractHandler::isHandling(array $record): bool

Now, I know that ShieldPro can’t fix some PODS code, and I also know that PODS can’t dictate how ShieldPro works, but I was wondering if someone (from both parties) could perhaps look into this weird issue.

From reading the above thread, then at least I am aware that the issue is being addressed.

OK, been digging after my crash report email came through.

Here’s a real poser ..
After updating the plugin SheieldPro.

Ultimate WP Security Protection – Scans, 2FA, Firewall, SPAM, Activity Log, Security Admin, and so much more.
Version 17.0.9 | By Shield Security

My website crashes out with the dreaded white screen of death, after renaming (wp-simple-firewall) to (old-wp-simple-firewall), ..

IT WORKS AGAIN.

(BUT)
From reading the crash report email .. its seems like it’s the PODS side that’s now causing new error.

Version 2.9.11.1 | By Pods Framework Team | View details
This plugin failed to load properly and is paused during recovery mode.

An error of type E_COMPILE_ERROR was caused in line 93 of the file /home2/b92couk/public_html/wp-content/plugins/pods/tribe-common/vendor/monolog/monolog/src/Monolog/Handler/FilterHandler.php. Error message: Declaration of Monolog\Handler\FilterHandler::isHandling(array $record) must be compatible with Monolog\Handler\AbstractHandler::isHandling(array $record): bool

Now, I know that ShieldPro can’t fix some PODS code, and I also know that PODS can’t dictate how ShieldPro works, but I was wondering if someone (from both parties) could perhaps look into this weird issue.

I’ve included this text on both support pages, .. hope you can help.

BTW – I’m running PHP version 8.0 if it helps.

Update:

After extensive testing, I can happily report that bbPress Forum is finally showing the all of the collapsed fields again ..

Editor width (brilliant to have it back again.)

All Fixed, and fixed on all Fronts.

Magic support and resolution, I really can’t praise the programming skills and dedication to this marvellous PODS plugin enough.

Many Thanks ..

Closing Ticket as ( Resolved. )

Anyone following this, all I can say is that support for this most amazing plugin is > superb: it’s >>*2.

I’m retired, and supporting that running costs of the plugin with a modest yearly donation: I’m gonna’ increase it next time round! – Absolutely Brilliant Response from Scott.

Keep the faith folks.

Yup! – Still having ongoing issues with the JS created input fields and labels.

Many thanks for your response ..

Hi yar — yar all, ..

Not a fix as such, but where the “More Fields” issue is concerned: changing this css:-

table.pods-admin { table-layout: auto; }

Does actually give me a bit more working room, but that label is still included on the same line: which is a major problem.

Still can’t get 2.8.x to work as 2.7.x did, and now it’s becoming frustrating.

Put all this on Slack
https://podswp.slack.com/archives/C02SVLHQF/p1636145122333400?thread_ts=1635261717.125000&cid=C02SVLHQF, but as yet: no replies.

Keep the faith folks! PODS is amazing, and I will get to the bottom of it.

Hi Scott, ..

Bad News I’m afraid.

Updated PODS on my local test-rig running WP theme 2012, unfortunately the problem remains unresolved.

Laters ..

Trying lots of things here with that ‘wp-mediaelement script’, so far no success.

But later on I’ll mosey on over there for a chin-wag, .. laters!

> What theme are you using?

Self inflicted theme I’m afraid.
From top to bottom it’s all mine.
I also have my site duplicated on a Local setup, and out there in the wilds.

The forums are closed off, and are available to registered users only.
I can set up a quick login if you wish, so’s you can have a look if you want, but for obvious reasons: I’m less than inclined to include it here.

> Do you see any JS console errors in your browser when you go to Inspect the page?

Nope, no errors at all.

Really flustered by not getting to the nitty gritty of this weirdness, usually can!