Marco van Wieren
Forum Replies Created
-
Forum: Plugins
In reply to: [WPO365 | MICROSOFT 365 GRAPH MAILER] unable to dismiss health admin noticeUnderstood. But when you navigated to the default settings page after clicking the admin-notice, a panel with the WPO365 Health Messages appeared, correct? The idea is that the general notice in WP Admin disappears, once you clicked “Dismiss all” on the WPO365 Health Messages panel. It’s just to be sure that you read those messages and possibly took action to improve the security of your site.
Forum: Plugins
In reply to: [WPO365 | MICROSOFT 365 GRAPH MAILER] unable to dismiss health admin noticeHi @dyin
I am glad you reached out and I am glad that you already found a solution!
The notice should link to the WPO365 configuration pages, and as soon as they open, the Health Messages panel should automatically open. At least that is how it is supposed to work. Did this not work in your case e.g. did the panel not automatically open?
Thank you for your attention and help to improve the plugin!
Marco
Hi @esszach
That is a fair point and I’ll investigate what options there are to indeed prevent it from auto-registering. Basically the Documents block is end-of-life and instead the recommended way to embed SharePoint files in WordPress is using one of the shortcode based embed-apps. I’ll consider adding an option to register the legacy block.
Thank you for bringing this to my attention!
-Marco
Thank you for your splendid 5* review and I am glad that I have been able to help! Integrating WordPress and Microsoft is not always intuitive and therefore I am here to help – for good or for worse 🙂
Best wishes
-Marco
Hi @jgwcouk
Thank you for your 5-star review and the absolute positive vibe of it! This is one of the best start in the weekend and will keep me motivated!
Best wishes
-Marco
Hi @tufty
Thank you so much for your five stars and lovely review – which is the best fuel for my engine and keeps me going 🙂
Best wishes
-Marco
Repo is now no longer publicly available.
Hi @gabbsmo
Just updating (and closing) this thread, in case others land here.
I have – with your help – identified an issue with WPO365 incorrectly assuming that WPML’s addition of a “virtual directory” for the language to the home URL – e.g. https://website/en/ – leads to an unsafe redirect target and therefore sending the user to the OIDC Redirect URI instead. The next release (either 43.5 or 44.0) will fix this issue.
Thanks you for your attention and support to understand the issue and test the fix!
-Marco
Hi @blackawxs
Thank you for reaching out!
Where did you find that link plus a description stating that this would be the official github repo for the plugin? You’re absolutely right that this repo has been used initially, but the current up-to-date open source repos can be found here https://wordpress.org/plugins/wpo365-login/#developers. The github.com repo is not longer maintained.
I will close the repo in the next couple of weeks and am grateful that you brought this to my attention.
Thanks!
Hi @gabbsmo
First of all let me apologize for responding so late!
I have tested your issue with the following URL https://domain.tld/wp-admin/admin.php?page=wpcf7&post=595&action=edit and it worked just fine. But I believe the issue is in your case is related to the redacted domain portion. Whilst redirecting the user back to the URL that they intended to navigate to – before the plugin initiated the SSO flow and redirected the user to Microsoft – it compares the hostname / domain segment from the Redirect URL (where Microsoft sent the user after they signed in with Microsoft) with the hostname / domain segment of the URL where the user intended to go. In your case, the plugin must have judge it unsafe to redirect the user to that specific URL.
If the issue still persists, then please
Please perform the following steps to collect debug information:
- Navigate to WP Admin > WPO365 > Debug and check Enable debug.
- Reproduce the error (ideally in a different browser tab).
- Now click the Refresh button on the Debug tab as soon as possible thereafter, click Download as JSON and send the JSON file to support [at] wpo365.com (in a separate file attachment).
I will analyze the JSON and try and understand what the issue is really about.
Thank you for your patience!
PS Don’t post the JSON results here as it may reveal sensitive data about your environment.
Hi @nonccorp
Thank you for this superb feedback, which helps me stay motivated and help customers to get the integration of their Microsoft tenant in their WordPress website right!
I am always happy to help and just let me know, whenever a new issue or question arises.
Thanks!
-Marco
Hi @digitalsabc
Thank you very much for your ***** star rating and wonderful review. And I have to agree with you: “Don’t do this when you’re sleepy” 🙂 My aim is to make it as easy as possible and explain with screenshots and videos, but if you paste one value or ID in the wrong field, then it’s difficult to get things working!
Thanks!
-Marco
Hi @aidanify
Thank you so much for taking the time to leave such a valuable 5 ***** review! That is much appreciated and hopefully for others helpful in deciding in favor of the WPO365 plugins for WordPress!
Best wishes
-Marco
Resolved and closing the ticket.