Mark Cutting
Forum Replies Created
-
Forum: Plugins
In reply to: [Theme My Login] If you update, going back to previous will not work@vansite thanks, but even 6.4 base doesn’t work for me. Too many database changes today to restore.
Forum: Plugins
In reply to: [Theme My Login] If you update, going back to previous will not workI have exactly the same issue. Got a HTTP 500 error (not related to Social Warfare as I do not use it), so rolled back to 6.1.14 – now /login /register /resetpass etc no longer work.
Forum: Plugins
In reply to: [Theme My Login] Will TML support social loginI’d also like to see TML have an option to request data and also delete the user account on the your profile page.
Forum: Plugins
In reply to: [Theme My Login] Will TML support social loginHi Jeff,
Despite all the overblown topics on the web, the compliance side is relatively simple. For example, at the register form, you’d include a field for arbitrary text, with a check box. The user cannot proceed without accepting the policy etc. I have something like this working for my Dev site using TML but a more native approach would be better in my view.
For the social login side, you’d prevent access to the OAUTH buttons unless the policy had been accepted on register.
Just a small observation – PostSMTP doesn’t seem to have a description when an update is released. My Simple Logging plugin tells me there’s an update for the plugin, but when the update completes, it simply says updated plugin “” to from 1.8.6 (also skips the latest release number)
Seems to be resolved with 1.8.9 🙂
Thanks
Confirmed. HTTP500 error
[24-Apr-2018 11:26:04 UTC] PHP Warning: require_once(Postman-Mail/PostmanContactForm7.php): failed to open stream: No such file or directory in /home/<em>redacted</em>/public_html/wp-content/plugins/post-smtp/Postman/Postman.php on line 57 [24-Apr-2018 11:26:04 UTC] PHP Fatal error: require_once(): Failed opening required 'Postman-Mail/PostmanContactForm7.php' (include_path='.:/opt/alt/php70/usr/share/pear') in /home/<em>redacted</em>/public_html/wp-content/plugins/post-smtp/Postman/Postman.php on line 57I’ve upgraded from 1.3.88 to 2.x. Whilst I do have some “residual issues” remaining, none of them have been insurmountable. My advice would be to attempt the upgrade on a staging site first to gain an idea of what is broken before doing the same in your production environment.
WP Roll Back is a good plugin that you can install beforehand so if things do go wrong, you can use this to revert.
@gfrow – for the raw html output in emails, have a look at this
https://docs.ultimatemember.com/article/1327-raw-html-issueThe loading loop sounds like a caching or minification issue. Do you have any plugins like this running ?
Forum: Plugins
In reply to: [WP GDPR] Do not override WP admin “postbox” CSS containerIs this released yet ?
The below CSS is causing serious padding overload in the admin panel
form.postbox, div.postbox {
padding: 30px;}
Thanks
Ooops – sorry !!
@donnyoexman if I disable your plugin, the admin screen is normal. If I enable it, the extra padding is enabled around the admin widgets
The padding:20px; line comes from the plugin CSS – see https://prnt.sc/j78ll6
Forum: Plugins
In reply to: [Cookie Information | Free GDPR Consent Solution] Support for wpDiscuz?@djpd I can confirm this to be the case. I’m using it with wpdiscuz
Forum: Plugins
In reply to: [Theme My Login] Unable to translateThat makes sense.
Thanks
@melkerh I’ve just tested this on my site, and have the same issue as you. It look as though this is being called
admin-ajax.php?action=um_router&um_action=route&um_resource=um!admin!core!Admin_Builder&um_method=dynamic_modal_content&um_verify=811ae66533But it’s not pulling any data – not sure why.
As I’m also affected by this (and have a developer’s bundle), I have logged a ticket:
“The live preview does not work when creating forms. The request is sent
wp-admin/admin-ajax.php?action=um_router&um_action=route&um_resource=um!admin!core!Admin_Builder&um_method=dynamic_modal_content&um_verify=811ae66533
But no data is returned. The newly created shortcode also does not work when applied to a page.”
The ticket has been submitted, so now we are waiting for a response.
Regds