Jan ?tětina

@maartenbelmans, given that there seem to be no known vulnerabilities in the plugin, your explanation (about exposing database to the admin) would make sense. Still, it would have been useful to communicate this more clearly, at the very least… and by protecting some people (specifically WordPress admins who IMHO can be expected to at least give it a second thought before installing any plugin) against themselves makes things inconvenient for everyone else. Instead of, say, asking for a big fat warning in the plugin description, and allowing everyone to decide for themselves with this information available.

I understand all this is debatable… but removing a plugin from the repository seems like a rather dramatic move, especially when the reasons are not explained clearly.

Just my personal opinions, of course. ??

This is really unfortunate. What is the point of the WordPress plugin repository, if not providing opensource, useful, safe plugins? As a user, I don’t care if it’s internally making use of another opensource project. Would my plugin be banned for embedding, say, a minified version of Bootstrap? It feels like an arbitrary decision to me (but please feel free to correct me if I’m wrong) – and I’m sorry it happened to you as a plugin author.

Beda, thank you for the clarification! In this case, however, I think we can escalate this directly, it is a small change without side-effects, and it makes good sense.

I see. We have a free forum as well, although I am not sure if it would make a difference in this case… please hold on a little longer, I will see what can I do about this. ??

I created an FTP account for you, please tell me your e-mail address (or write to [email protected]) so I can send you login information.

PHP version is 5.5.10.

The only issue so far is this one… nothing on the admin side or elsewhere, as far as I know.

Yes, that’s the correct theme. Thank you very much for doing this!

I found the following:

• WP_DEBUG unfortunately doesn’t reveal anything related to your plugin.
• I took extra care when experimenting with your code, function was cut from function td_tts_userAjax() { to it’s last }.
• Montezuma does call wp_footer() as it should.

The affected site is https://oporavnouzi.cz/. I could arrange for you an read-only access to it’s source code if you think that would help.

Maybe it is also worth saying that the site runs under lighttpd web server, not apache. I am suspecting the heredoc syntax might be somehow involved in this error…

Well, I tried to change wp_footer into wp_head and the warning still appears (but at the top of the page this time). I think that if wp_footer action hadn’t been called, WordPress wouldn’t even try to call td_tts_userAjax. Montezuma is a big theme, lot of code. I will examine it tomorrow if it is needed.

But there is something really strange happening. Why does php die with a syntax error “unexpected end of file” when I move source code of td_tts_userAjax function to another file?? That usually happens if some brackets aren’t closed… but in that case the syntax error should happen every time, even without the modification, right?

I see the error on bottom of every page on the front-end. Even if no other plugins are active. I use the Montezuma theme and I am quite sure that this error happens when wp_footer action is called.

Concerning the wp_enqueue_script, you are right, I think it’s just a “best practice”.

Hello, I’ve just released version 2.0.4 with some fixes and the issue you encountered should be covered as well. (please confirm)

As of now SuH should be compatible with 3.8.1.

I am sorry for the delay, there hasn’t been much of a free time recently.

Fixed in 2.0.4, thanks for notifying me.

Please check your PHP version. Do you have >= 5.3? Since Superadmin Helper version 2.0 it is a requirement.

Your assumptions are correct, WLS_TXS is a typo, should be WLS_TXD (textdomain). I’m going to practically rewrite the plugin soon, so please be patient.

As for the PSR-3 wrapper… that sounds very interesting. Thanks. I’ll probably implement it as well.

Thanks for your information. Please be patient now, this plugin’s code is in quite bad shape and needs some major changes.

Yes, that would be great, thanks!

POT file is not included because of small, but frequent changes and me allways forgetting to update it. ??

You can use for example the Codestyling Localization plugin to create the translation files.

Oh, my mistake. Please try 2.0.2.