sydatbliz

Problem isn’t happening with 4.4.6 so I’m marking this as resolved.

Voxel uses the Gantry framework. Rockettheme have just updated the Gantry framework to fix its issues with NextGen.

The issue was with the Gantry framework – RocketTheme have just updated the Gantry framework to fix the problem.

The issue was with the Gantry framework – Rockettheme have just updated the Gantry framework to fix the problem.

The Gantry framework for WordPress has just been updated to version 4.1.2. It fixes the incompatibility issue with NextGen Gallery.

Reflex uses the Gantry Framework which has issues with NextGEN 2.0.63 and 2.0.65. However 2.0.61 works fine.

I’ll add my voice here – both 2.0.63 and 2.0.65 have broken any Gantry based site I’ve tried them on and all display a “>” at the start of the page as described above, they also lose all css styling. WordPress 3.9

BTW – You can turn off those email notifications in the ‘Intrusion Detection’ tab of Better WP Security. The information in the logs is really only useful for reference after you’ve been hacked anyway, and even then they may not reveal anything to someone not versed in security.

It means what it says – files in your wordpress site have changed. This can happen if you make changes on your site, upload new images and add, delete or update plugins or update wordpress itself…. and there are probably many other reasons too (including the rare example of hacking).

Given the number of changed files it looks like either WordPress itself or one or more complex plugins have been updated. You can check this by looking at the log files that you can access under the Better WP Security menu in the WordPress backend.

You’ll find a link to a list of the changed files in the logs. In most cases you’ll see that it’s just plugin updates. Depending on your WordPress setup, WordPress itself may update automatically so large scale file modifications can happen without you doing anything at all.

Same issue here. Has stopped working on every site where I’ve made the upgrade.

Hi Alexey

The upgrade has simply broken other things. Each of the products that were supposed to have 2 checkboxes now have 3. The 3rd one belongs to the product that had only one checkbox.

Most of checkboxes returned the “Please select Volume at first” message when I tried to add them to the shopping cart.

I decided to change one product’s selections from checkboxes to a pulldown menu and now that pulldown menu appears with every product. The pulldown only works for the product I gave it to however. The other products display a non-functioning pull-down but still have their own checkboxes as well.

I’m going to try a fresh install of the plugin on a clean wordpress install and re-enter the products but I suspect your plugin is badly broken – each time I try to make a change to one product it affects the others in unpredictable ways.

Same problem here. I use shortcodes to display products and use checkboxes to select the product size variation. After the update the shop page is now showing eleven checkboxes for each product, most of the checkboxes without descriptions.

To clarify – I currently have 4 products, 3 of them have two size option checkboxes (e.g. 500ml and 750ml) and the 4th one only one variation.

Fortunately the shop is only in development on my localhost (MAMP) and not yet live.

Clicking any checkbox and adding to cart produces this error message: “Please select Volume at first” Depending on which checkbox you click that message will be repeated one, two or three times.

As with Jerry’s comment there’s no way to edit or delete the additional parameters.

Tested in WordPress 3.5.2 and 3.7.1 – same error in both and the problem persists when I change the theme.

Never mind – after about 4 hours the problem has resolved itself but I’d still be interested in an explanation if it’s obvious to anyone from the error message. BTW – the entire error message not just the “There are no tweets to display for this user.” was displayed in the sidebar.

Thanks, Syd

Thanks, for the detailed reply shortj. Hope they get this sorted.

shortj

I can see your shop is now working. Did you simply use an older version of the plugin or did you find a different solution?