tosca30

Same problem here. I tried different settings, but the same image is always posted when there is no featured image, even with Auto unchecked and No image selected.
I tried to implement to og:metadata with this script in functions.php but it doesn’t seem to change anything.

Thanks a lot for your answer.

Thanks a lot for your quick answer. That will do for now. ??
I just had to use it in emergency, for a theme that has not been localized.

I’ve downloaded the Plane theme, but the languages folder is empty. Where can I find the fr_FR translation?
Thanks for your answer.

Thanks for the fix, I was worrying and wondering about what has gone wrong in my site…

Same here, I saw this when I activated the debug mode:

Strict Standards: Declaration of SLB_Lightbox::_options() should be compatible with SLB_Base::_options($options_config = NULL) in /home/centresoj/www/site/wp-content/plugins/simple-lightbox/controller.php on line 7

Strict Standards: Only variables should be assigned by reference in /home/centresoj/www/site/wp-content/plugins/simple-lightbox/includes/class.utilities.php on line 623

I still have another capability issue, following this thread.

For a custom taxonomy that only administrators can modify, I’ve defined the following capabilities:

["manage_terms"]=>
    string(14) "manage_options"
    ["edit_terms"]=>
    string(14) "manage_options"
    ["delete_terms"]=>
    string(14) "manage_options"
    ["assign_terms"]=>
    string(10) "edit_posts"

However:

1. whether I put the menu location for this taxonomy in either the Settings or the Appearance menu, a line still appears in the chosen menu even when the user role has no manage_options capability. And if the user clicks on this line, he get the message
   

   Alors, on triche ?

   on a blank page, so he must use the navigator back key in order to go back to the admin. I’d rather he doesn’t see any menu at all.

2. in any case, when assigning terms to a post, a user is still able to create a new terms, whatever his role, though only the administrator has the manage_options capability

So I’m unable to protect this taxonomy against modification as the capabilites don’t seem to work at all.

I create the new role with the Roles & Capabilities panel, and I assigned it the same capabilities as the Editor (those that are displayed – see below), plus the following:

• add_users
• create_users
• list_users
• promote_users
• remove_users

All the pods capabilities are unchecked, but this role seem to have them nonetheless.

Another strange thing is the Manage Roles panel says Editor has 35 capabilies, and Manager only 34! But none all of them are displayed on the Edit Role panel… I’m a bit lost here!

I’m a bit puzzled because the display doesn’t seem consistent…

It is an event date that has been created as a custom date field for a custom type event with the Pods extension.
There might have been some caching issue or whatever because the date seem to be correctly displayed now for all the events that have been created more recently.

Thanks, this will be a very interesting addition.
When do you think this new release will be available?

It is ok for standard articles and pages, but I can’t see the UPM option on custom post type articles.

It doesn’t work for the euro symbol: €, I get a ‘?’ instead.

Same problem here with the 1.2.31 version.
There seems to be some user cache problem, because if I logout, then relog the drag&drop works again for a few times. Then I need to logout again, etc.

Hi Scott. Thank you very much for your input. The cache clearing did the trick and I’ve been able to check that the capabilities have been actually added to my custom taxonomy.

A var_dump for the taxonomy object shows the following:

["cap"]=>
  object(stdClass)#2021 (4) {
    ["manage_terms"]=>
    string(14) "manage_options"
    ["edit_terms"]=>
    string(14) "manage_options"
    ["delete_terms"]=>
    string(14) "manage_options"
    ["assign_terms"]=>
    string(10) "edit_posts"
  }

But these capabilities don’t seem to work when the taxonomy is been used in the admin interface. Only the administrator role has the capability to manage options, so any user with another role should only be able to assign terms, and nothing more.

I guess the problem is probably on the WordPress side (or my understanding of it…), but if somebody has any idea about this issue, I’d be very glad to hear about it.

Thanks again for helping.

@joeathomas

Thank you very much for your suggestions.
I tried the first one (using pods_wp_taxonomies filter as explained here) but it doesn’t seem to work. I’ve put an echo statement in the function for debugging, but nothing shows on the screen.
The filter doesn’t seem to be used, either when creating a new custom taxonomy, or when editing an existing one.
I think this should be the right solution, provided I can make it work.

About the Roles and Components, I don’t see how it can be a solution. It allows to create new capabilities, but there is no way to link them to custom taxonomies.

And removing the menu is not a solution either, as nothing will prevent new terms being added in the post edit views. Only the right capability can guarantee that the taxonomy won’t be modified from anywhere.

I will appreciate any idea to make the pods_wp_taxonomies work properly.
Thanks for helping.