schneeb

I am getting the same error with a live site. I had an ad block that was working fine before the update, but since 3.8 has not functioned:

Warning: shuffle() expects parameter 1 to be array, integer given in /*url removed*/wp-content/plugins/adrotate/adrotate-output.php on line 268

Warning: Invalid argument supplied for foreach() in /*url removed*/wp-content/plugins/adrotate/adrotate-output.php on line 302

Also, my stats are still not displaying. I haven’t cross referenced the database, so I don’t know if the data was removed entirely or just not showing. Since updating to 3.8 yesterday, it has not added any stats although the ads have definitely been seen.

If it helps to know, the split testing plugin works on the client side and should not interfere with a cache plugin.
https://www.ads-software.com/extend/plugins/optimizely/

I thought it would be painful and time consuming, but it was actually quite easy. You can simply view the page source or use a browser plugin such as firebug to determine the files. I did a simple search both for ‘.js’ and ‘.css’ and then began adding those files to the corresponding list. It may be best to do it a few at a time to determine where the conflict is arising.

I ended up resolving this issue:

Under General Settings, I set Minify to manual. Then under Minify, I specified which JS/CSS files to minify, so it doesn’t effect the scripts I still needed to function.

This actually proved to be very beneficial, because I was able to determine a few other plugin conflicts it was causing that I was able to correct.

Even if someone can point me in the right direction, that would be wonderful!

I would also like to know this answer.

In my case, I have the login form embedded on a different page using this method – https://www.wprecipes.com/add-a-login-form-on-your-wordpress-theme

The form works fine without the plugin enabled. With it enabled, the captcha doesn’t show on my embedded login, and you are redirected to the main login page where an error message says the captcha is incorrect. Perhaps I need to add a bit of code for the hook to work properly?

I had a feeling that would be the answer…
Thanks for making such a great plugin ??

Just installed the updates and the fields are now being remembered!
Thanks again ??

No need to apologize, that sounds great! You are doing a fabulous job with the plugin so keep it up.

I’ve found this post here – it looks like they are aware of the problem and working to fix it in the next release. ??

It’s a fabulous plugin & I have heavily modified it to suit my needs. Since I haven’t had this problem before, I’m just not entirely sure where to start to find a solution!

large plugin based features that I know will require database modification.

I suppose I should have reworded that. I didn’t think they would change existing structure. I originally thought it would be easiest to re-upload the entire db structure from the test site to the live site. It looks like this is not the case.

How would you personally handle using plugins that will need to be populated before launching? (Such as plugins that will display organized lists) Would I populate it on the test site, run a query to copy those new entries, and then insert them into the live db? (I suppose there would be a potential for error, but I could always try this method on the test site.)

Thanks for the quick response!

When you talk about uploading in phases, would I test a plugin then install it onto my live site OR would I test a plugin then replace existing live site files? While the latter would be easier, it could run the risk of deleting a new user who had just signed up while I was testing…

I’m planning to launch new areas of the site in the future – large plugin based features that I know will require database modification. This is the main reason who I am so thrown as to how this should be handled! ??