trejder

Nope, I don’t use this plugin. I didn’t even know, there is such plugin at all.

I have got the feeling, that your plugin’s buttons are hidden by standard WordPress toolbar. But since, the entity, which is hidning them, is empty, then I’m not sure, what is this.

At current version set (WordPress 4.3 + plugin 0.9.5) everything seems fine — Add Media and other buttons seems to be working just fine.

@jkhongusc: I don’t know, what version I do have now (becaue I don’t have any access to dashboard and I don’t know how to check it other ways). Downgrading to earlier version is not an option for me. I want to have all security issues covered, so I always install newest available version.

@jan Dembowski: I don’t know, how to check it, but I’m pretty sure, that is not an issue. Mainly because:

• domains and redirects are handled by mu-plugin, and described problems are also present with this (and all other plugins) completely disabled,
• if this would be caused by incorrect redirect / domain configuration, why did it collapse after recent update, not many weeks or months ago (I just check it, that I have this blog network for nearly two years)?

Thanks for all your effort once again, by I’m beginning to think, that total wipe and starting from the scratch is the only way in this case.

Jan, thank you for your effort and attempt to solve my problem.

I’d like to not disclose my network address / domain right now. For privacy and security reasons (especially, that disabling plugins made all sites open to all visitors). Maybe in a private message, but not public, not now. If it will be required to solve the problem, then I’ll paste all required URLs. But, for right now, let’s try to do this “virtually” (if there is anything to do, except reinstallation, cause this thing really looks strange).

I have “disabled” all plugins, as you requested (by renaming “wp-content/plugins” to “wp-content/plugins-old”; I don’t have any “mu-plugins” folder). This has caused following effects:

1. All pages are now accessible for guests, instead of displaing landing page (thanks to “underconstruction” plugin being disabled).
2. Network dashboard (https://example.com/wp-admin/network/) again redirects to home page (https://example.com), but this time displays info, that there are no pages instead of landing page.
3. Any site admin page (https://domain.com/wp-admin/index.php) again redirects to URL: https://domain.com/wp-login.php?redirect_to=http%3A%2F%domain.com%2Fwp-admin%2F&reauth=1 and also displays “Page Not Found” page.
4. Attempt to open login page (https://domain.com/wp-login.php) ends up with browser ERR_TOO_MANY_REDIRECTS error and warning message, that page contains too many redirects. Suggested solution (clearing cache and cookies) does not work.

I haven’t tested directly calling login page (https://domain.com/wp-login.php) previously (with plugins “enabled”) so I did this now. When plugins are enabled, there is no error/warning. The “underconstruction” plugin takes its part and displays landing page.

I have never seen error suggested by you (“You do not have sufficient permissions to access this page”) at any point during my tests. I have tested this problem on all three browsers, to which I have access. I have cleared cache and cookies in two of them (can’t do this in my main browser). No effect, as for now.

Is there anything I can do in this situation?

Please note, that I’d like to recover entire network and those 30-50 posts already made. But, on the other hand, vision of dumping everything and starting from scratch isn’t some kind of nightmare for me. So, please, only spend your time on my case, if you really think, there might be a solution or if this case can benefit others. Thank you in advance!

Damn, once again “hit” by stupid WordPress “preview” mechanism! ?? Of course, everything is fine with both Jetpack’s Markdown module with SyntaxHighlighter Evolved plugin, once you hit Update button to finally update the post. All described problems happens only, when you’re using Preview Changes button.

Damn, once again “hit” by stupid WordPress “preview” mechanism! ?? Of course, everything is fine with both Jetpack’s Markdown module with SyntaxHighlighter Evolved plugin, once you hit Update button to finally update the post. All described problems happens only, when you’re using Preview Changes button.

I manage to fix this problem myself! All you have to do, is to change line 430 of wp-content/plugins/markdown-quicktags/js/quicktags.jquery.js from:

if (ev.ctrlKey || ev.metaKey) { // && $.browser.safari

to:

if ((ev.ctrlKey || ev.metaKey) && !ev.altKey) { // && $.browser.safari

If you’re using WordPress 3.2 or older do the same trick in line 428 of quicktags3.2.jquery.js.

Issue is resolved, but author should include this changes in official release, as he has promised over a year ago.

As I may see (this issue), you have been informed about this issue a year ago and though didn’t introduced any change.

Pity, because Markdown QuickTags really looked promising and I was hoping to use it. But, since you weren’t interested in introducing tiny fix for over a year, that means you don’t want to support nor further develop this extension anymore. Pity…

Just take a quick look into this plugin source code and you’ll find, that it is pretty simple. I don’t remember, if it does anything else than just registering one action. You can then copy this action (or entire source code, if necessary) to your selected theme or functions.php file or anywhere else, where user-contributed actions are registered.

Thanks, Henk! :]

With your example, I was able to find out, what was wrong with my code!

T.

Thank you @all for all precious opinions and advices, but in my current situation, you missunderstood purpose of my post.

I don’t have problem with spam on my blogs. Current configuration works just fine, and if it would fail, I have always Gmail’s filters as second line of attack.

I’ve just noticed information about SPAM-preventing techniques that binds together Contact Form 7, CAPTCHA plugin and akismet. Enabled it on my company blog for a test purpose only and immediately noticed, that this team is just not working as it blocks correct e-mails from being sent.

I just wanted to warn others. You can easily spot false positives, which is spam not catched and delivered to you. But it is way harder to find out false negatives, where legit message is tagged as spam and thus not delivered.

I was lucky to catch such situation and so I was able to disengage this spam-preventing team. But there might be many people out there, that will want to run it on their company blogs, and will not be aware that this can possible block their customers from sending them letters.

That’s just the whole story.

Thanks again for anything and sorry again for a bit offending words.

@lemonthirst: you’ve completely misunderstood my post.

SPAM was detected by Akismet, on WordPress side! E-mail never reached my servers. It is problem of Akismet, Captcha plugin or their both cooperation, not spam filters, as message in decribed case is never sent and never leaves WordPress.

Funny thing is, that when I used test case scenario (sending as “viagra-test-123” in sender name), Akismet catched that as SPAM correctly. But, when I used different sender, but exactly the same string in e-mail, subject and body, message was delivered without problems and blocked on my Gmail, spam filters side. Neither WordPress nor akismet comply nothing about sending message with [email protected] sender address or “viagra-test-123” in subject or body.

This proves, in my opinion, that catching spam in contact form using both akismet and captcha plugin still have a long road before it, until it will finally be usable. But, that’s my private opinion.

Very, very sorry for using inproper words here! ?? Won’t happen again.

I’ve posted information here, because I noticed problem directly in CAPTCHA plugin. I have enabled akismet integration in this plugin and it failed to sent legit e-mail. I informed users here, because they may not be aware, that enabling aksimet in captcha to prevent spam (what is discussed here) can cause normal e-mails to not pass-through.

I’m not willing to get into touch with aksimet support, because there is not support at all there. There is a thread opened (in which I took part), where someone is proving that akismet is sending private blog’s and user’s data, sensitive to security, to their own servers, without any reason. And non of the akismet moderators, admins or creators has responded in such important thing. After that I’m really thinking about dropping akismet at all.

But the reason to post here, not at Akismet was, to inform that captcha-akismet integration fails on certain occasions. If I would wrote that there, they would probably reply me, that this is releated to captcha plugin, not akismet.

Cheers, and sorry for offending words again.

Not yet. Page is under heavy reconstruction and though is not available for not logged-in user. It should be ready within 2-3 days and I’ll share URL then. Thanks.

This DOES NOT work for a corporate / company sites!

Perfectly correct, non-SPAM message (though cooperation offer) is marked as SPAM and not delivered to the company.

Either Akismet or Really Simple CAPTCHA fails on this.

Big ******, if talking about company website, if you loose potential customer, only because of such stupid error, that he can’t send you initial cooperation offer.