benknight

Thank you for the quick follow up and also thank you for all the hard work you’ve put into this plugin. Much appreciated.

Follow-up, sorry this was indeed related to a full-page caching feature provided by our host, SiteGround. Thanks for the tips.

• This reply was modified 3 years, 2 months ago by benknight.

A few suggestions (I literally just published this plugin, so I appreciate your feedback and patience!):

1. The plugin uses the menus you create in Appearance > Menus, and it only uses the ones that are assigned to your Theme’s Locations in the left column of the Menus screen.
2. The plugin requires that your server is using PHP5. It won’t work with PHP4

I’m using Rackspace Cloud Sites which is a managed hosting platform, but according to their docs they run Apache v2.2 (https://www.rackspace.com/cloud/cloud_hosting_products/sites/technology/)

WordPress 3.2.1, File Gallery 1.6.5.6

Recently installed and was disappointed to have to disable the minify module completely due to various problems, almost all of them browser-specific.

No my issue was with the “multiple specific” selections, but now I see it there so it looks like it either previously required the dev version of WordPress or they rolled it out with a new plugin update.

I’m surprised there’s not more discussion about this. Am I just not seeing something correctly? The plugin specifically mentions in its description the ability to do “specific multiple image uploads”, yet I see now mechanism for doing so. Can I get a witness?

Well done gentlemen… I struggled through this troubleshooting process myself. Adding that function on the parse_query action indeed works, but it leaves me wondering, is this a bug? It must be, because this is happening contrary to expectations under default conditions.

It makes perfect sense why this bug is there though. I guess the solution would be modifying the core to check when the ‘category’ taxonomy has been registered on other post_types, and if so changing the ‘post_type’ parameter to ‘any’ instead of the default ‘post’. A good question to test would be to see if this bug exists whenever taxonomies are shared across post_types – should we always expect that taxonomy queries will show any post that has its terms assigned to it, or just the posts of the post_type that “own” it, such as how the ‘post’ post_type “owns” the ‘category’ taxonomy, but shares it with other post_types cause its a nice guy.

Through further troubleshooting I was able to determine that this was being caused by a user account in the database with no email address set even though it’s required. I think this stemmed from a previous data import.

Anyway, just a heads up – the get_user_by_email function was always returning this user row because it was being called with blank data which was causing login errors.

I’m also wondering if you have any plans to add support for caching? This is a great plugin but I really need it to support custom taxonomy queries and caching. In fact I’ll probably end up coding it myself since I don’t see any other decent JSON WordPress plugins. If I extend the plugin would you be interested in having that code?

Here’s the CC docs regarding uploading CSVs:
https://constantcontact.custhelp.com/cgi-bin/constantcontact.cfg/php/enduser/std_adp.php?p_faqid=2523

Essentially there’s no strict formatting guidelines – it will accept any CSV in which there’s a column of email addresses. They also have information regarding contact details and a reference for which headings to use, but this is optional.

As I was troubleshooting the plugin, I ultimately narrows my CSV file down to one column of email addresses, followed by one column of numeric IDs (integers, no quotes) and the results were that WITH the column of IDs, the upload failed, with an error message of “Invalid Request”. Removing the column of IDs resulted in a successful import of the contacts.

I can email you a copy of the CSV file I used for testing if you like!

Thanks for your quick reply.

Ben

This is also happening to me – custom category templates all break when this plugin is activated, which renders it useless despite the awesome functionality it has.