mikele3

thank you for improving Sagawa and JP-Post

you are correct about Yamato, my mistake…
Yamato needs the tracking number submitted as $_POST data …

in another application, I pass the anchor href in this format:
https://toi.kuronekoyamato.co.jp/cgi-bin/tneko?1234-1234-1234
to a jQuery function, like this:

let 
 url = href.split('?')[0],
 tracker = href.split('?')[1],
 form = new Array;

form[0] = '<form target="_blank" accept-charset="utf-8" method="post" action="' + url + '">';
  form[1] = '<input type="hidden" name="number01" value="' + tracker + '" />'
form[2] = '</form>';
$(form.join('')).appendTo('body').submit().remove();

very well, I’ll sit tight.

PS: for multilingual I use WPML
I hope you can make it so that customers can access SAGAWA and YAMATO tracking services in Japanese unless the customer is viewing the website in any other language than that. … or at least always in Japanese and not in English

never mind.
I come to realize it is a no issue.
??

Apologies.
It was a misconfiguration on the server side.
All good now.

@as247 you were correct, your plugin works as expected; I was doing the authentication wrong.

Sorry for the late reply, it just took me this long to figure it all out.

@specialk, thank you for your quick and clear reply.

I like and most importantly trust your plugin, but I understand I’ll have to find an alternative for this project.

Best regards.

I am doing like you said.
Thank you!

thank you Tijmen,

I did fiddle with settings for a while, then I decided to delete and recreate the keys.

Eventually I removed restrictions on the key and proceeded with the CSV upload, then added restrictions back.

Apologies for looking for support for the add-on here, I’ll use the support link you posted if I need further help.

absolutely!

in .htaccess I had:
RewriteCond %{REQUEST_URI} /+[^\.]+$
RewriteRule ^(.+[^/])$ %{REQUEST_URI}/ [R=301,L]

I had to add two lines (one each language in the website) and the rule now looks like this:
RewriteCond %{REQUEST_URI} /+[^\.]+$
RewriteCond %{REQUEST_URI} !^/wp-json
RewriteCond %{REQUEST_URI} !^/en/wp-json
RewriteRule ^(.+[^/])$ %{REQUEST_URI}/ [R=301,L]

After all day debugging, googling and learning about wp rest API, I figured out where the issue was…

I have a rewrite rule in my .htaccess to add a trailing slash to URLs, this is what was causing the 301 redirects

I added a line to exclude /wp-json and now the plugin works just as expected.

thank you for your time and support.

Best regards.

All In One WP Security:
https://www.ads-software.com/plugins/all-in-one-wp-security-and-firewall/

BBQ Pro:
https://plugin-planet.com/bbq-pro/

Disable Embeds:
https://www.ads-software.com/plugins/disable-embeds/

Disable Emojis:
https://www.ads-software.com/plugins/disable-emojis/

the theme is self made.

plugins quite a long list:
Advanced Custom Fields PRO
All In One WP Security
BBQ Pro
Contact Form 7
Disable Embeds
Disable Emojis
EWWW Image Optimizer
Hyper Cache
Media File Renamer
Menu Item Custom Fields
Regenerate Thumbnails
Simple Image Sizes
Simply Show IDs
WP Media folder
WP Media Folder for Lightroom
WP/LR Sync
WPML Multilingual CMS
WPML Translation Management

hello Takayuki san,
sorry for the late reply, I forgot to check for follow-up notifications.

using Contact Form 7 V4.7, an AJAX call is made to https://jewelry.rin-kg.com/contacts/ and emails are sent successfully.

using Contact Form 7 V4.8, there is first a POST to :
https://jewelry.rin-kg.com/wp-json/contact-form-7/v1/contact-forms/3498/feedback
that triggers a 301 response followed by a GET to the same URL that generate a 404 and this Response:
code “rest_no_route”
message “No route was found matching the URL and request method”
data Object
status 404

thank you for your attention.

Hello @chesio

you are right, sorry! I overlooked that those strings were changed.

thanks again for the help!
Mikele

Hi ?eslav, thank you for the quick reply.

I replaced the function in my script and added echo in front of it; works perfectly.

I still have to patch the plugin on every update to fix my issue with the email that is sent after the unlock request…. do you think the small changes I suggest will ever be considered in the next updates?
(copy and paste from above)

bigger problem for me (as it might/will break with updates) is with:

static function send_unlock_request_email($email, $unlock_link)
I had to comment that out and rewrite my version.

my issues are:

$subject = '['.get_option('siteurl').'] '. __('Unlock Request Notification','all-in-one-wp-security-and-firewall');

get_option(‘siteurl’) returns the url to the WP installation not the website’s base url
even then, I would have preferred the website name… I changed that to:

$subject = get_bloginfo( 'name' ) . ' ' . __('Unlock Request Notification','all-in-one-wp-security-and-firewall');

and I had to broke down into smaller parts $email_msg in order to be able to provide translations through WPML.
this:

$email_msg .= __('You have requested for the account with email address '.$email.' to be unlocked. Please click the link below to unlock your account:','all-in-one-wp-security-and-firewall')."\n";
would have been made available for translation as : “You have requested for the account with email address [email protected] to be unlocked. Please click the link below to unlock your account:”

so I did rewrite it as:

$email_msg .= __('You have requested for the account with email address ','all-in-one-wp-security-and-firewall');
$email_msg .= $email;
$email_msg .= __(' to be unlocked. Please click the link below to unlock your account:','all-in-one-wp-security-and-firewall')."\n";