diyafury

I have done, thanks: https://wpforo.com/community/wpforo-showcase/php8-upgrade-causes-a-conflict-with-the-woocommerce-pdf-voucher-plugin/

@garconis it’s not ideal by any means but for a temporary solution you can change the ‘required’ values on lines 216 and 221 of class-gfklaviyofeedaddon.php to false in gf-klaviyo-add-on plugin directly. Tested and managed to submit a new contact to my klaviyo list.

I’ve got the same issue… please change this. The only fields that are required is either an email or a phone number that I can see from the api documentation.

Hi there

– Advanced > Authenticate filter worked perfectly. The error message displays correctly with the ‘resend email’ link. I click on the link, get an email… click the verification link in the email and is logged in – no drama!

Thank you so much for sorting this out for me… I can now push live!

Great plugin, great support!

• This reply was modified 3 years, 9 months ago by diyafury.

Hi there

We’re using a child theme of DIVI. I’m not sure it is theme related, perhaps I am misunderstanding the process.

This is what I am expecting:

1. Existing unverified user goes to login screen…. (No message displayed)
2. User tries to login… receives an error message saying that they need to click on a link to verify their email address and check their email.
3. User receives verification email
4. Clicks on link in verification email
5. Logs in

What I am getting:

1. Existing unverified user goes to login screen…. (No message displayed)
2. User tries to login… receives an error message saying their credentials are invalid — nothing about verification.
3. User receives verification email (only the first time they try to log in)
4. Clicks on link in verification email
5. Logs in

Hi there I’ve tried enabling this but it did not work.

We use the Woocommerce myaccount page (which will show the login/register screen) when not logged in.

I have noticed that when an unverfied user is logged in, I manually unverify the user and then log the user out, I get the ‘activate’ message be cause a query string param is added to the url ?alg_wc_ev_activate_account_message=16361

If I add this query string param to the myaccount page (login) then I get the message too, however it seems that this is not automatically added.

Any ideas?

I also had this issue after updating my instagram feed plugin… (and upgrade to WP 5.5) on the updates page, so I deactivated the Smash Balloon Instagram Feed plugin, went back to the updates page to see if that fixed the issue… it did. Then reactivated the instagram feed plugin, checked the updates page again. Errors gone.

Hi there

I have a similar issue, however I got my site working with https by setting the https through cpanel > Let’s encrypt. When I try to enable https via SG Optimzer I get the “COULD NOT ENABLE HTTPS” error.

My first question is this… would SG Optimizer throw the “COULD NOT ENABLE HTTPS” error when https is already enabled via cpanel as it is in my case? Basically I prefer to set it with SG Optimizer so if I switch the https toggle off in cpanel and then try and enable it in SG Optimizer, will it work?

Question 2: I would like my staging environment to be https, but because of the way the Siteground staging copies work, enabling https in cpanel only does it for the the main domain. Enabling https via SG Optimizer caused my staging environment to explode presumable because the domain is configured to the main domain (not the staging domain)? Anyway I can get this to work?

Cheers
Nadia

The exact syntax I had to use was:

ini_set(‘display_errors’,’Off’);
ini_set(‘error_reporting’, E_ALL );

Nothing seems to actually be broken so switching off the display errors will certainly do for now.

Cheers for that ??

Hi there

The error only started happening when I updated the alm plugin (I needed the meta_compare bits), the older alm version worked fine with out errors, I think it was version 2.6.3 – I wonder if it is a similar issue as per this one: ALM is Throwing strtolower() Error at Beginning of Loop (2 posts)

The piece of code from the plugin that is throwing the error (revision-control) since the alm update is this:

if ( !empty($_REQUEST[‘post_type’]) )
$post_type = stripslashes($_REQUEST[‘post_type’]);

The warning pops up on every ajax request the alm code makes it seems.

Both plugins are vital and are used on an existing site – I’m literally adding a few extras which required the alm plugin update.

Do you have any recommendations on the best way to resolve this?

I’m not sure where (looks like PTO), would need to debug. I’ll just leave the Admin sorting for now it’s not essential.

Thanks for the great plugin.

I’ve discovered where the issue lies, not yet sure how to fix it.

In the Post Types Order plugin there’s an Auto Sort setting and an Admin Sort setting… it turns out both needs to be unchecked for ALM to work. This seems to me a bug as the Admin Sort setting should only apply to the admin front-end but seems to be affecting the website front-end where ALM is concerned.

Basically my orderby attribute seems to be ignored completely when Post Types Order is used. Both plugins are the latest versions.

Hey there

I have a similar issue but seemingly the opposite is happening for me – I’m using Post Types Order and I’m using Ajax Load More for search results. Originally I had Post Type Order automatically re-order my wp_queries (a config setting of the plugin) resulting in my search results being ordered by date instead of relevance. I switch the Auto ordering off for Post Types Order and manually added orderby=’menu_order’ where needed (not in search).

I have added orderby=’relevance’ and order=’DESC’ to my ALM shortcode and assumed that with auto ordering off my results should now appear correctly, however the post order of the results remain ordered by date. When I deactivate the Post Types Order plugin completely my results are ordered correctly by relevance.

I really do need both plugins. Any ideas to what might be going on would be greatly appreciated.