manare

Thanks for your answer.
However, costumer’s server is so low cost that the hosting provider won’t allow increasing that limit.
Currently, max_execution_time = 30

Hi.
Thanks for your answer.

Obviously, that malware code did not come with your plugin! It was injected yesterday due to the attacks I’m suffering.

Sorry for having posted that malware code, I just did it in order to let you see whether it was generic code or malware code adapted to your plugin (and I could not attach the file). I was not actually asking for help, but just thinking I could be of help if I’d show you what it had been added to that file. ??

Sure thing, I’ll be buying a pro licence as soon as I change my current host provider (I believe their firewall is almost non-existant).

Cheers,

Hi again.
I’m still having issues though using Cloudflare.
I’m writing just to let you know something that perhaps you may improve in the future (if it depends on you, of course).
Among my -once again- infected files, this time I also found one which belongs to your plugin and that it became infected:
module-help-hack_protect.php

I think it’d be good if this plugin of yours could find a way to protect itself against modifications (if feasable), otherwise, that it’d include perhaps a file checksum everytime it runs (or every X-given time).

Here’s the code I found in the above mentioned file, hope it helps (no idea what it does):

<?php $fed7 = 374;$GLOBALS[‘ac9b8d9d’] = Array();global $ac9b8d9d;$ac9b8d9d = $GLOBALS;${“\x47\x4c\x4fB\x41\x4c\x53”}[‘v77f2a87’] =

[rest of code deleted — please do not post malware code]

• This reply was modified 6 years ago by manare. Reason: non easily readable injected code on top if inside code tag
• This reply was modified 6 years ago by Steven Stern (sterndata).

Hi.
Thanks for your prompt answer.
WP File Editing: Yes, the slider shows “green”, but when I check it at “Overview” it says it’s disabled. So, that’s why I added the “define” line to my wp-config.php file.

Backdoor: I understand what you say. The plugin protects a clean website, but if there’s already a troyan script inside somewhere..- then I’m done. It’s obvious.

I guess my site is compromised (5868 transgressions in just less than 3 days), so it’s really difficult to upload my backup copy and install your plugin right away without being already infected. If my wp-config.php file was compromised, then my DDBB must be infected too. I don’t know how to proceed not to be infected again during this short period of time when your plugin is being installed and activated… these bots are too fast for anyone.
I’ll delete it all over again and upload my backup + your plugin. Let’s cross fingers.

Cheers,

Hi there,
Same issue here with: qtranslate-x.3.4.6.8 + Yoast SEO v3.7.0 + Integration: Yoast SEO & qTranslate-X v1.1.1

However:
Once you’ve entered your tags and snippet for each language, save your changes.
When you swap among your language tabs, you will only see the snippet and tags in one only language.
You need to press F5 everytime in order to refresh the metatags info in every language tab.
Confusing when you see it for the first time, but at least, it keeps the correct tags for each language.

BTW, I tried to install this pre-release (v1.2) but it crashed and could not be activated:

Fatal error: Cannot redeclare qwpseo_init_language() (previously declared in /var/www/vhosts/mysite.es/httpdocs/wp-content/plugins/wp-seo-qtranslate-x/wordpress-seo-qtranslate-x.php:19) in /var/www/vhosts/mysite.es/httpdocs/wp-content/plugins/wp-seo-qtranslate-x-1.2/wordpress-seo-qtranslate-x.php on line 29

Cheers!

• This reply was modified 8 years, 4 months ago by manare. Reason: missing info
• This reply was modified 8 years, 4 months ago by manare.

Hi Takayuki.
I see. It does not have this problem with a default theme.
I managed to solve it today by overriding this:

span.wpcf7-form-control-wrap {
    display: inline-block;
    vertical-align: top;
    width: 100%;
}

with this:

span.wpcf7-form-control-wrap {
    display: inline;
    vertical-align: baseline;
    top: 6px;
    width: 100%;
}

I wrote my solution here, just incase somebody else faces such problem once.
Can’t understand though that the inline-block results in a line break with my current theme.
Cheers,

Hi.
Same issue here.
Trigger was an unsuccesfull plugin update from admin page via FTP.
Plugin SiteOrigin Widgets Bundle 1.6.4 failed to update and then all I was able to see was a blank page with maintenance message. No way I could access any page, not even admin page.

Same solution applied. Thanks spanizhfly… I was shocked! ??