Viktor Nagornyy

@shayleehansen30 I checked the latest version of NF and it doesn’t have “ninja_forms_render_form_attrs” filter. Is this a correct filter to use?

Check plugin description, the first “Live Demo” link. It’s a broken URL. See screenshot.

@oakleaf101 you will have to go back to version 1.7.5 if you want to use OceanWP with ClassicPress v1.

https://downloads.www.ads-software.com/theme/oceanwp.1.7.5.zip

ClassicPress v2.0 is currently under active development, which is based on WP 6.2 (minus the blocks and FSE). So with v2.0 you will be able to use more recent version of the theme but I have not tested any yet. If you want to test v2.0 with OceanWP, stop by ClassicPress forums or Slack ??

Thanks for the great plugin. Sad to see it go. If possible, please do make the last version available for download on the website… in case anyone needs it. Or a link to a GitHub repo where the last version can be downloaded, or for someone to fork it.

They pushed 1.5.2 out, but it still doesn’t work for me. Can you confirm if 1.5.2 fixed the issue for you or if you still experiencing it?

@dreampress you’re right. It appears developers do not use tags for versioning, so they only submit the latest version. There’s no way to roll it back unless you have a copy of the 1.5.0 version.

@bellabludesignshoppe as a quick fix, you can either deactivate the plugin or downgrade to the previous version so you don’t lose sales. I submitted a ticket to AC support, but they tend to be slow over the weekend.

Same here. This error is causing problems with PayPal payment gateway. Orders can’t be completed and paid through PayPal because of this error. Disabling AC plugin fixes the problem and orders go through.

@makewebbetter was this fixed? We have version 2.0.0 and still experience this issue. The is_order_bump_purchase: true is included in the customer emails. Also, this is being added to our PDF packing slips that are generated by WooCommerce PDF Invoices & Packing Slips.

Thanks.

• This reply was modified 3 years ago by Viktor Nagornyy. Reason: spelling correction

@kgmservizi any updates on this? thanks.

Thanks, looking forward to seeing an update.

Sorry, I was traveling. For reference, I believe it was OPCache causing a delay in templates updating correctly. After 5-10 min, templates would begin working correctly.

@milindmore22 thanks, I appreciate this.

There seems to be an issue with object cache and disabling sessions, in our case Redis. If I disable sessions with Redis object caching enabled, I get 502 error and PHP error log shows this:

PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /wp-content/plugins/helpful/core/classes/class-helpful-helper-values.php on line 192

I’ll need to do more testing over the next few days, but thought I’ll mention it.

Samesite cookie seems to be working. Thanks.

@jdembowski thanks for a detailed reply, I understand where you’re coming from. Borrowing your Barbossa example, he knows what the code is, to begin with. I think that’s really my point and concern. How can you expect users to follow or even know about guidelines if they don’t know about them when they register?

As a moderator you want users to follow the forum guidelines. They can’t follow what they don’t know about. So giving them an opportunity to read them when they register would help the user and the moderators. It can be as simple as redirecting them to the welcome message page (maybe that’s already happening, I haven’t registered in years).

This also applies to changes to guidelines. When guidelines are changed to include new information, it’s only fair to let users know. It can be a simple notification bar at the top of all the support forum pages for a few days, or a simple modal notification when the user logs in and dismisses it.

All I ask is for you to consider these to help users and the moderators. There’s really no downside to this, only the upside.

Thanks!