hooohn
Forum Replies Created
-
Hello @webnus – thanks a lot, it worked!
Best regards from GermanyForum: Plugins
In reply to: [SSL Mixed Content Fix] Problem with custom fields: links are not displayedHey Steve, thanks for your reply.
I actually deactivated your plugin since, but reactivated it now and will have a look.OK, thank you. A least that’s a workaround that will do for the time being.
Best regardshi,
this would take quite some time, as I can not force WordPress to do that internal test;I can tell you that I do not have issues on sites where either there is e.g. WP AIOSF with another theme or Yootheme Pro with e.g. Wordfence installed.
It is this combination – WP AIOSF & Yootheme Pro – that causes the error message.
As I said, Yootheme is aware of the issue but they seem to be unable to fix it.
thanks and best regards
Hello,
thanks for the quick reply.I was not able to determine if a single function is the cause.
The error message I sent you is the same for all the sites using this theme/plugin combination.
Thank you & best regards
Forum: Plugins
In reply to: [Shariff Wrapper] Nach Update auf WP 5.2.1 keine Shariff Buttons mehrHallo Markus,
Leider nein; inzwischen werden die Buttons in den Posts wieder angezeigt, nur innerhalb eines Widgets nicht.
Vermutlich liegt es am Theme im Zusammenspiel mit dem Plugin WP All in One Firewall & Security, aber weiter bin ich hier nicht gekommen.
Hello @patrickposner
thanks for the quick reply!
I discovered the failure (do not know if it occured during that) when I tried to update the site with WPMain. so WP Main child is one of the plugins installed.
The site was down with the 500 internal error then.
I deactivated all plugins and switched them on again once I could log back in.
passster was the only one I could not re-animate. The error message shows up everytime I trie to activate it; wordpress does not let me activate it anymore.On this site, I do use a couple of plugins, but really no fancy stuff. there is
- all in one Security
- Advanced cusotm fields
- Antispam Bee
- Autoptimize
- Borlabs Cookie – Cookie Opt-in
- Classic Editor
- Display Posts
- Duplicate Post
- Duplicator Pro
- Google XML Sitemaps
- Gravity Forms
- HTTP / HTTPS Remover
- MailChimp for WordPress
- Post Type Switcher
- Postman SMTP
- Statify
- Related Posts for WordPress
- Widget Options
- Widgetkit
- WP Super Cache
- Yoast SEO
your help is very appreciated
Cheers,
Robthx! appreciate your quick reaction!
Solved!
I had changed the header of the site to be GDPR-compliant (DSGVO in German) and added:
<meta name="referrer" content="no-referrer">in the<head>-section of the template.Once removed, the password protection works again!
Thank you all for listening ??
Hello @patrickposner,
although unfriendly uttered, I appreciate your help and have subsequently revised the review.
If you want to avoid future missunderstandings, think over your GUI and functionality and do not blame users for not understanding what you mean.
Your “customer relationship” management needs massive improvement; even in a open source community like WP your behaviour is untolerably bad and childish.
Do not go out into public if you can not manage it.
Forum: Fixing WordPress
In reply to: Password Protected Pages Go BlankI have the same problem but uploading a new wp-login-php does not work for me. Any new suggestions on this one?
Hi @wpsolutions,
thx, I will check with the hoster and post any reply hereHi @mbrsolution,
ok got it, while not sure how to deal with JetpackThanks for your answer @mbrsolution.
Indeed I have Disable Pingback Functionality From XMLRPC enabled, I use Jetpack and the WP Mac App to monitor the site(s).
As I understood the comments above, there was to come a whitelist bugfix for some Apache servers that was supposed to help fix this blacklist issue.
Any news on this?
Do you suggest to use the Completely Block Access To XMLRPC function as a workaround? I don’t quite see the connection between XMLRPC and the blacklist feature?!
Thank you
Problem remains after update…
please help
For the sake of completeness, this is the relevant Apache version:
2.4.6-45.el7.centos.4Does this match your expectation?