Iulia Cazan

Hi,
Please upgrade to 8.0.4 and let me know if the issue has been fixed.

Regards,
Iulia

Hi,
Thanks for letting me know. I will attempt to replicate and push a fix with the next release.

Regards,
Iulia

@macmanx, I reopened the issue as it seems this is still replicable in 6.7 and now maybe it seems more relevant https://github.com/woocommerce/woocommerce/issues/52646

Additionally, for some plugins the text domain do not get picked up anymore, regardless of the hook used.

Does anyone know where is the new/updated documentation regarding the plugins translations – if available – after the new changes introduced in 6.7?

• This reply was modified 1 week, 5 days ago by Iulia Cazan.
• This reply was modified 1 week, 5 days ago by Iulia Cazan.

Hello,
I haven’t heard back from you in a while so I will mark this as resolved. You can start a new thread if you have other questions.

Regards,
Iulia

Hi,
Renaming or disabling the plugin temporarily would work as well, no need to delete the plugin (after you login and activate back the plugin you can change the allowed IP from the plugin interface). If you have access to the database, there is a combination of options you could change manually.

Regards,
Iulia

Hi Mark,
That is a feature in the PRO version.

Regards,
Iulia

Hi,

The PRO plugin is not available for download on the www.remarpro.com repository. If you are using the update feature from the wp-admin plugins screen, the files of the plugins are replaced by the version downloaded from the www.remarpro.com repository (the free version).

Regards,
Iulia

Are you accessing the page with an admin user, or has something changed for your user capabilities?

Hi,

Please update to 6.6.0, I made some changes to the firewall. Let me know if this is working for you.

Regards,
Iulia

• This reply was modified 1 month, 1 week ago by Iulia Cazan.

Hi,
To me it looks like some login session or nonce expired. Have you tried to logout and login again on the site?

Regards,
Iulia

• This reply was modified 1 month, 1 week ago by Iulia Cazan.

@leemon, I marked it as resolved because it makes sense we are updating the hooks in our code.
Initially I did switch to using after_setup_theme hook, and it did not work, the translations were not picked up. After playing with the hook priority (do not leave it to the default priority), I got it to work as intended and also the notices are gone. So, this was a false positive issue, using the hook suggested in the notices makes things work as intended, but only when we do some higher priority.

• This reply was modified 1 month, 3 weeks ago by Iulia Cazan.

I could test and understood better the nesting. You could try with the gap attributes instead default_gap="1.5rem" https://imgur.com/a/5oB8TwQ

Let me know if this helps.

Regards,
Iulia

Hi,

I am not sure I understand well your setup. The hspace does not seem to be related to the LPS attributes, maybe you need to use default_padding="1rem". Can you send a link to your page where I can check the output or some screenshot of how it looks now and your shortcode string?

Regards,
Iulia

Hi,
I did not get any notifications from the Loom application about reply on my comment. Based on the feedback you provided now, I presume it’s a browser cache, since accessing the image directly you get the expected crop (the file itself has been processed correctly based on the crop position you put in the settings).
Have you attempt to purge all browser cache for the page, or tested from a different browser where you did not previously open the page?

Regards,
Iulia

• This reply was modified 2 months, 1 week ago by Iulia Cazan.
• This reply was modified 2 months, 1 week ago by Iulia Cazan.

Hi,

Looking at the markup I saw that the margin is added to the hentry, maybe you could try this instead:

#custom_html-7 .latest-post-selection.two-columns {
    grid-auto-rows: auto !important;
}

#custom_html-7 .hentry {
    margin-top: 0 !important;
}

Let’s see if this helps.

Regards,
Iulia