Marco van Wieren

Closing the issue due to inactivity.

Hi @dyin

Since WPO365 is not able to set the “from” address to an address other than the account that you initially authorized to submit WordPress emails to Microsoft Graph or any other account that the authorized account has been granted permissions for (to send on behalf), your only option to make this work, would be to specify a reply-to account in the email template in WooCommerce. That reply-to account must be equal to the customer’s email address. So my guess is that here something changed. I just quickly checked whether WPO365 does respect the reply-to header and didn’t find anything suspect.

Hope this helps!

-Marco

Hi @ericscoles

Since this concerns a premium package, I recommend that you contact us directly either via the Help Beacon that you find in the form of a question mark “?” at the bottom of each configuration page or via the contact form on our website. Those channels are monitored and you’ll get a reply much sooner!

I quickly checked and the error is caused by the fact that you have WPO365 | MICROSOFT 365 GRAPH MAILER and WPO365 | LOGIN installed and activated at the same time. Please deactivate WPO365 | MICROSOFT 365 GRAPH MAILER and try again to activate LOGIN+ and you’ll see that it works as expected.

WPO365 | MICROSOFT 365 GRAPH MAILER is a spinn-off of the WPO365 | LOGIN plugin and the latter contains the exact same mailer functionality, plus a lot more. So if you plan – for example – to utilize the Microsoft Graph Mailer and Single Sign-on (SSO), then WPO365 | LOGIN is the right choice.

Hope this helps!

-Marco

Hi @akahky

Sorry for my late response! For urgent matters, please use the Help Beacon that you can open with the question mark “?” on the right bottom of each WPO365 configuration page in WP Admin.

Before I can adequately answer your question, I’d like to understand what yo wish to achieve. Your question here is “Cannot access REST APIs”. It is possible that this is the case because you configured the Intranet Authentication scenario (on the plugin’s Single Sign-on configuration page). If you selected this specific scenario, WPO365 redirects the request to – for example – https://your-website/wp-json/wp/v2/posts to Microsoft. To avoid that behavior, you must add /wp-json/ (or a more specific path) to the list of Pages freed from authentication (also on the plugin’s Single Sign-on page).

If you wish to enable authentication for a WordPress REST API endpoint, then you can either configure Entra ID based authentication (see https://docs.wpo365.com/article/147-azure-ad-based-protection-for-the-wordpress-rest-api) or WordPress cookie based authentication (see https://docs.wpo365.com/article/151-wordpress-cookies-based-protection-for-the-wordpress-rest-api). Please note that some of these options are premium paid options and require a WPO365 addon or bundle.

Hope this helps!

-Marco

Hi @cefcwebmaster

Thank you for taking the time to leave this review and your 5* rating.

I am sure that will definitely help others as well as keep me motivated!

Best wishes

-Marco

Hi @mgaetano2000

Thanks a lot for your feedback and and I really appreciate the 5* review and your comment in regard to the support provided!

Best wishes

-Marco

Thread closed according to user.

Closing this topic as we continued “offline” to be able to share sensitive information.

Closing this topic because no further replies were received.

Hi @spalders

Thank you so much for your 5*-review. I am always happy to assist, especially because of the complexity that surrounds an integration of WordPress and Microsoft Entra | Azure | 365.

Best wishes

-Marco

Hi @jesusistruelord

Thank you for reaching out! Please check https://docs.wpo365.com/article/36-authentication-scenario. You’ll notice that you can add the following snippet to your wp-config.php to prevent the plugin from being loaded when you have configured the plugin’s Internet Authentication Scenario.

define( 'WPO_AUTH_SCENARIO', 'internet' );

Please note that adding this line to your wp-config.php may also prevent some (premium) functions e.g. to detect restrictions configured for a page to work as expected.

The script is loaded on every page load, because it inject important JavaScript dependencies in the page, to allow for a login button being placed on every page.

Hope this helps!

-Marco

Hi @cgscomputers

Sorry for my late response. I missed the question at the end!

You can definitely add it as “/wp-admin/admin.php?sig=”. Maybe it is also possible to define a prefix for the sig value that is always the same and then you can at least add that as well. Or you can add all different signatures for all child sites, but obviously that is depending on the number of child sites.

Hope this helps!

-Marco

Hi @thnurg

Any update on this from your side?

Thanks!

-Marco

Hi @wolfstettler

Can you please let me know if you have been able to resolve the issue or whether you still need support with this issue?

Thanks!

-Marco

Hi @quinze

You’re absolutely right! Not sure how that was missed, but it was!

Thank you for bringing this to my attention. Version 28.2 has just been released and should fix this.

Hope this helps!

-Marco