Mirco Babini

Can’t replicate anymore or not happening on other sites.
Probably site related.

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the mainwp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the awesome-support domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /public_html/wp-includes/functions.php on line 6114

• This reply was modified 4 months, 1 week ago by Mirco Babini.

Even worse. Fixing the fatal results in:
– upload working when managing tickets from back-end
– upload NOT working when creating/replying a ticket from front-end

Just opened a ticket on their paid support portal as well.

• This reply was modified 5 months ago by Mirco Babini.

Same here. Flushing the object cache is ok.

Same issue. I fixed this by adding two cap to my user.

$user = wp_get_current_user();
$user->add_cap( 'hicpo_load_script_css' );
$user->add_cap( 'hicpo_update_menu_order' );

• This reply was modified 9 months, 3 weeks ago by Mirco Babini.

Or maybe just telling the UI the error is something with the exec, and let me run the command manually (then activate the options even if in a manually manner).

Those custom fields are not editable from there (free version of the plugin). They released an update with the fields disabled.

Then it’s a (missing) feature, not a bug.
Lol. Somehow this is solved, then.

Not fixed yet. Not even got in contact with them though. It’s just a shame you have to get in contact via facebook). That’s a poor experience. Also, the final solution will not be readable by others.

Mh, I’m using Advanced Columns Pro which might be related to the cookie issue.
Btw, that’s just a side effect; if you fix the missing user issue, I think we are done.

Thanks!

That makes sense but doesn’t solve the issue. You are still placing a nonce verification into an action which does not require a nonce verification at all.

I perfectly understand the implications of an unsafe ajax request, but that’s just an ajax to load an html form. The nonce verification must be in the following step (the login data submission).

Also, it’s not possible to act the way you suggested: we placed the Login button in the header of the website, then it’s in every single page of the site. It’s not a matter of which page is cached or not.

Also, the nonces validity is 12-24 hours but there’s NO alignment with the cache. Even if I refresh the cache every hour at 00, still there are some minutes in which the nonce will not work (from when the nonce expires, to the next 00).

Then, this is not a solution at all.

Happening on a Siteground Cloud Hosting.

Another reason might be that somehow people are trying to cancel twice. The second hit comes when the sub is already cancelled, causing that weird message. We do have a javascript trick to avoid double-clicks on the “cancel confirmation” page but sometimes the double cancellation still comes. Not an issue at all, btw. Just a notice.

Also check this related support request: https://www.ads-software.com/support/topic/cannot-create-a-user-with-an-empty-login-name-4/

I would suggest to try getting in touch with them (PayPal) from the Merchant Support Portal. https://www.paypal-support.com/s/?language=en_US

Just follow the “Contact us” section and you gonna have a reply (with an investigation on some of your requests) in just a few hours.

I would also get in contact with your hosting provider. Just guessing here.