Jory Hogeveen

Hi @fauchelafleur

WPML would handle syncing the metadata in such a case, however, it would not handle translation. Did you enable translations for media files? If so, it might be that the media items selected for the translated post are filtered out because of the media language.

Let me know!

Cheers, Jory

Hi @grigorax

Could you share the method you use to create/display the link? Are you using Pods Templates for example?

Cheers, Jory

Hi @pelemanindustries

I actually noticed this myself too in some occasions, thought it was a glitch or something and forgot. Since you report the same behavior I’ll take a look at what is going on here.

Cheers, Jory

Hi @manuel1610

By setting it to true you are actually disabling it. Try setting it to false and PHP will work again. But as mentioned, this is deprecated so I would suggest switching to the helper functions as described above.

Cheers, Jory

For reference to other users seeking help.

This was related to Elementor. Apparently Elementor doesn’t run date parsers through WordPress translations. Switching to a Pods shortcode instead of an Elementor Dynamic tag fixed this issue.

Hi @webiaprodg

Since you’ve already posted on our support channel and on Slack I’ll keep the conversation on Slack and post any solutions on your support thread: https://www.ads-software.com/support/topic/i-want-date-in-french-no-english/

Thanks! Jory

@studiotwee

You’ve mention guideline 18. These guidelines are IMO not in line with current circumstances so yes, I would definitely call this theft.

1. This is definitely not a fork, it’s a (hostile) takeover.
2. They didn’t just take over, they rebranded.
3. The reason they gave is a recent (small) security issue which ACF has already patched for some time. ACF was denied access to the repo to be able to upload it here… This is just plain gaslighting to public.

Now to be clear, I’m definitely not pro WPE.
But as @dmje also already stated, actions like these are not acceptable in any situation, regardless of a fight between these two companies (who IMO are both in fault here).
From my point of view, also taking into account the history between these two giants, this whole fight is clearly about money and has nothing to do with open-source.

• This reply was modified 1 month, 1 week ago by Jory Hogeveen.

Hi @rbdev

Sorry that you didn’t receive a reply on this topic.
Good to hear that you’ve got the job done!
Not that it’s of any use now anymore, but a plugin that I can suggest in the future is WP All Import and WP All Export.
Also the default WP Importer can also import CPT, though the export file will need to have this defined in the data so you probably need to do a search and replace.

Cheers, Jory

Hi Jack,

Ah check! I didn’t notice that it was AJAX related as well.
Thank you for the prompt reply and actions!

Thanks, Jory

Hi @kaiserigen

By default, users that are able to “view as” will not show in the results. Though I don’t think this is what you meant right?

If you use the filter you can define which roles another role is allowed to view. Keep in mind that users that are able to use this plugin are still excluded!

“Our Sales Agent should be able to purchase viewing as a customer assigned to them.”
How is a customer assigned to a sales agent? If access management is done properly then users not assigned to the agent should automatically be filtered out. ( ‘edit_user’ capability check )

Cheers, Jory

Hi @hesseldejong

I’ve been testing and researching these issues and this looks like it’s related to the login cookie.
View Admin As does not change the login cookie, it only switches the user within WordPress at a really early stage. Therefore the cookie is still linked to the original logged in user which is also cached in View Admin As so the admin bar menu is still available.

Why this does work with the REST API using the Block Editor but not with your plugin is still a mystery to me. I would think that both use the same routing and validation process.

Cheers, Jory

Hi @jltest

This is not really a hook for Pods but more for WordPress in general. You can use it in your theme PHP code or a plugin. More on hooks here: https://kinsta.com/blog/wordpress-hooks/

There are also Pods specific hooks like: https://docs.pods.io/code/action-reference/pods_api_post_save_pod_item_podname/

Cheers, Jory

Hi @jltest

In case the Smart Slider plugin is not even considering supporting an ID then you could hook into the update meta functions and set your own values:

https://developer.www.ads-software.com/reference/functions/add_metadata/
https://developer.www.ads-software.com/reference/functions/update_metadata/ (update changes here)
https://developer.www.ads-software.com/reference/functions/delete_metadata/ (remove generated meta value if original is deleted)

You can get the image URL here: https://developer.www.ads-software.com/reference/functions/wp_get_attachment_image_url/

However, in regards to relational data it’s more common to store an ID to make sure all validations are parsed correctly. This also will support various image sizes etc. so it would be better of the slider plugin would support ID instead of URL’s. Even WordPress core stores the featured image as an ID.

Cheers, Jory

Hi @wilbertschaapmancom

Do you mean the PDF’s themselves are posts? Or are they fields from a post?
Otherwise said: should the page not show any results at all for visitors or should it display the posts but without the PDF link?

If they are posts then you’d need to use custom PHP code or a plugin to restrict access. There are many membership/access plugins available, both free and premium.

If it’s just related to the page content (eg: custom fields) then my previous answer could help.
Alternatively, since you use the Beaver Builder: the Beaver Themer allows conditionals per module/row: https://docs.wpbeaverbuilder.com/beaver-themer/1.4/developer/conditional-logic-apis/
This might also be an option to look at.

In any case, Pods doesn’t include a built in access management UI for it’s fields or content.

Cheers, Jory

Hi @wilbertschaapmancom

Pods only has settings for visibility in the admin. In regards to the frontend you would need to create your own logic for this.

In case you use Pods blocks etc. you could use a helper function.

Only logged in users:

function yourCustomHelperName( $value ) {
    if ( ! is_user_logged_in() ) {
        return '';
    }
    return $value;
}

You can use this in any location where custom helpers are supported in Pods.
See: https://docs.pods.io/displaying-pods/magic-tags/#Passing_values_through_callbacks_and_filters

How are you currently displaying these fields?

Cheers, Jory

• This reply was modified 3 months, 1 week ago by Jory Hogeveen.