Jason Judge

I’ve also raised this with Woothemes, but their ticket system is located behind some kind of black hole, so I can’t provide any kind of ticket number or link to point you at discussion there.

I installed this plugin on WP 3.4 with the debug bar on – it fills the admin pages with lots of warnings, so is probably not something that should be used without some TLC.

However, as a workaround – and this seems to work – add ANY taxonomy that you want to search for terms to, to the POST post type, as well as your custom post type.

So I have a taxonomy called “artist” that is linked to the products in the shop of post type “product”. In order to search on the artists when searching the shop rpoducts, I need to link that same taxonomy to the “post” post type. That seem works for me, and hopefully it will be helpful to others.

I just found this too. I’ve posted more details here:

https://support.advancedcustomfields.com/discussion/3268/deleting-a-single-field-removes-the-entire-field-group

This plugin is brilliant ??

It has not been updated for several years, so is it dead? I’m hoping not.

Doh! It’s named in the csv_post_type field.

Does this mean a single CSV file can import data for multiple post types?

I haven’t changed anything on this plugin for a while, but will be getting back to it (hopefully) in October. In the meantime, give it a go and report back if it does not work as expected.

Thanks,

— Jason

Hehe – I would have done it for four ??

Seriously through, glad you got it sorted. Software is like that – you type one single character that it does not like, and it won’t forgive you. You always need to make sure you have a way to back out again, and that means backing up files before you change them.

Oh, and if you have given out access passwords to people you don’t know, make sure you change the passwords once they have done the job.

If all you have changed is functions.php, then just restore that file back to the original copy. If you didn’t take a backup before fiddling with it, then extract it from the zip file of the WordPress version you installed originally.

There is certainly an error in the code that was pasted, on line 144. We can’t tell you what that could be, because we can’t see line 144. We have no idea what line 144 is. Perhaps with some clues, we could help.

There is a syntax error on line 144 of includes/functions.php That is where you need to look first.

@kelly – that’s a useful technique, but does it not rely on the “wordpress_logged_in” cookie being created by the WordPress installation? The problems I see are:

* This technique assumes that if the cookie exists, then the user is logged in. Since a user can create any cookie they like, they could simply create the cookie and get through this check.

* The check does not distinguish between different roles for users logged in. It assumes that ANY logged in user has access to all the uploads. This includes users that have registered to upload a CV and so get access to other users CVs.

I think the way to do this is to redirect ALL upload URLs through a script that checks the roles the user has. The difficulty is the way the CVs are mixed in with all other uploads, including images and other documents that should be freely available to anonymous users.

Thanks for sharing – it is a step towards finding a solution, which may involve a separate plugin to secure uploaded files according to roles.

— Jason

The Player works fine, also with files larger than 5MB. And the constantly crying is more annoying than a red line in the WP backend. You should use another plugin.

“Here is a potential issue, a warning, and a suggestion.”

“No there isn’t, don’t care, and sod off. Oh, and thanks for the contribution, but sod off anyway.”

Nice business model. Still, your prerogative.

I can’t get any of the JavaScript help pages or “more options” to work on 3.2.1. This is a fresh install, and so how it works is still a complete mystery to me, what with not being able to get to the instructions for use. Am going to have to move on and try another plugin.

It probably would, and I can see how useful it would be (the relationship of one map per page or post that the plugin imposes may be useful in some circumstances, but other times multiple maps on a page would be very handy.

It would probably need some changes in the core plugin though, because only the width and height are accepted as parameters in the pronamic_google_maps() function.

Another approach could be to put maps into hidden posts, and pass the post ID as a parameter. That way there is not too much work involved having to extend the parameters to include everything you may possibly need in a map (title, name, coords, addresss…). A post type called “maps” would work, though making post types that WordPress does not automatically index and make available to the world is a pain.

Anyway, there are some ideas, so hopefully they will land on the right lap for some implementation ??