jstneti
Forum Replies Created
-
Hey,
Thanks for the quick reply. I was sick but replied today after checking – it’s sadly still not working.
OMG, I feel so dumb right now. Thank you kind stranger, that was it. I did not even think of this.
Forum: Plugins
In reply to: [WooCommerce] PayPal redirects to thank-you with login formThanks for a quick response.
I was testing logged in as admin, not guest user. Now I tried again as a guest user and it worked fine.
I guess it must be something with my admin user.I don’t personally use PP Standard but a client uses it and I came across this when doing some tests.
Thanks again.
I missed the “Batch process” tab. It works great.
I also found the Support tab so all good.Thanks
In the WP description, it says Pro gets you Priority support. But where can this support be accessed?
Forum: Plugins
In reply to: [AutoPoly - AI Translation For Polylang] EDIT: Chrome built-in AI not workingThanks for the update.
I was sure I replied but I guess not. I confirm that the grayed-out button and 301 redirects were from another plugin even though the plugin was deactivated during testing. Only after uninstalling that plugin, the issues went away.
I am using the latest versions (Free and Pro) and I get the notice:
[09-Jul-2025 09:07:16 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for thewpvivid-backuprestoredomain 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 theinitaction 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 6121Forum: Plugins
In reply to: [LiteSpeed Cache] WPML redirects issues with latest versionSent. Here is the report number: CORINLYU
I cannot trigger it now. If it comes back, I’ll check.
I’ll do some more testing before I open a support ticket. Maybe it’s another plugin, like WPML.
It’s been some time since WP 6.7 made this mess. The plugin cannot be used until it gets resolved because it’s throwing errors elsewhere.
Will the update be out soon?
Thanks. I have sent the email with admin access to a new site via email.
Yes. It does. I already tried that first thing when it happened.
And this is not a single occurence. It also happened on another site but I can’t share the link publicly. If you share an email, I can send you the BookingWP plugin to test.
Hi,
I tried clicking String Translation but got no options to do anything.
The form is dynamically added to the product page. The issue is with the product page.
Here is an example from a test site. You’ll need to open Dev Tools to see what I’m talking about. Search for “wc_appointments_field_data_início_month” string in the Elements tab. This is the translated name of the input field. It should not be translated. It’s a name of an input field, not shown to users.
The original name is “wc_appointments_field_start_date_month” and that’s what the plugin expects to receive when submitting the form. But it receives a translated version.
Another vote for this.
Forum: Plugins
In reply to: [Payment Plugins for Stripe WooCommerce] PaymentRequest not workingThanks for the fast reply. Happy to hear the feature still works.
I used a live HTTPS domain that’s accessible with password only (staging) so I will notdisclose the URL just yet.
Btw, Google Pay (test mode) works, but PaymentRequest not. I’ll try to convince the client to get a merchant ID since Google Pay works. Let’s see how it goes.