Jory Hogeveen

Hi @jltest

When both pods are enabled in Polylang for translations it should filter the relationship results by it’s language.

So if a hotel is in BE language it should only display areas in the same language.

In case you are editing an object that doesn’t have a language you can use the language switcher at the top toolbar.

I just verified this behavior in another installation of mind which has both Pods and Polylang running on the latest version.

Could you verify and make sure this issue occurs even if you have only Pods and Polylang activated?

Cheers, Jory

Hi @gep123

This is currently not included in the plugin settings but meant as a manual task. Simply because 1) this plugin doesn’t include and design additions and 2) every site has it’s own design and elements.

I personally add an off-canvas-sidebar trigger within the sidebar that wil close the sidebar when clicking on it. After that you can manually add some CSS to design it to match your theme.

If you use the legacy widgets there is a widget included in this plugin. If you use the newer block widgets you can use a shortcode: https://github.com/JoryHogeveen/off-canvas-sidebars/wiki/Shortcodes

Cheers! Jory

Hi @reventlov

Thanks for checking and verifying!
Just to be sure, you can reproduce the same behavior with all other plugins deactivated?

If so, then in that case it’s definitely something else so it would be helpful to have a staging environment where we can do some more thorough testing.
In case you are unable to create a staging environment I can do this for you so you can install and recreate your environment there.

Please note that the WP forums do not allow sharing any login info of any kind.
You can reach me on Slack, GitHub or through keraweb.nl to continue.

I’ll make sure to keep this topic updated with any relevant information about this issue.

Cheers, Jory

Hi @reventlov and @rogierlankhorst

Just ran some various tests with VAA active and inactive but I cannot seem to reproduce this issue.
Once I’ve added the capabilities I can access the Burst pages and the REST responses all return a 200 status. Even when trying the same for a Contributor role which barely has any capabilities this seems to work perfectly.

For this reason I doubt that View Admin As is the actual issue here but it might be a combination of other plugins.
@reventlov Can you reproduce the issue with only Burst and VAA active? And if you can, do you have the option to create a development/staging environment where you can reproduce this from scratch with only Burst and VAA active?

Cheers! Jory

Hi @smeleka

Just a heads-up that I’m closing this topic since it’s become stale.
Feel free to contact me on any further questions!

Cheers, Jory

Hi @reventlov and @rogierlankhorst

Jumping in on this topic as the author of View Admin As. Do you have any pointers for me I could check for to find the compatibility issue? I use this plugin together with many other plugins to test switching roles etc. without issues so I’m wondering why you have issues with the results while switching.

@rogierlankhorst Could it be that you validate the current user’s capabilities in the plugins_loaded hook with a very early priority?

Cheers, Jory

Hi @smeleka

The impersonated user is actually the current user when you’ve switched to a user view.
While this plugins does support user switching this feature is not the same as impersonating a user for ordering.

I also consider this out-of-scope because such a feature it’s not actually switching, it’s placing an order for another user.
Even with custom modifications from GPT I’m unsude whether you could use my plugin for such a feature since it’s functionality at it’s core is simply very different.

Ofcourse I could create an addon or something and I would consider this provided that such an addon doesn’t exist already.

I’m on holiday right now so can’t respond quickly unfortunately. Thank you for understanding.

Cheers, Jory

Hi @jjmontalban

Ah you mean the full admin bar.
This is currently not a feature of this plugin simply because it isn’t supported by WordPress.
As a visitor you have no capabilities so even if you were to show the admin bare through a custom PHP filter it would probably be empty.

Here is a plugin that should always show the admin bar, even to visitors: https://www.ads-software.com/plugins/always-show-admin-bar/
May I ask what you are trying to do? I don’t understand why you would need an admin bar as a visitor.

Cheers, Jory

Hi @jjmontalban

This is actually default behavior.
If you have a view enabled on the front-end but the admin bar is not visible by default you’ll see a small eye icon on the top right of your screen. That is my placeholder toolbar so you can still use the plugin.

Cheers, Jory

Hi @johannesdb

Thanks for the reminder, I’ve been absolutely swamped with work.
The release has been published just now!

Cheers, Jory

Hi @mableb

You use-case would not be documented yet, but you can read more about magic tags here: https://docs.pods.io/displaying-pods/magic-tags/

Not sure how you could implement this further but you could add some JS vars like this:

<script>
var fieldname = '{@field_name}'; // For anything text based.
var fieldnumber = {@field_number}; // For numeric fields (without quotes).
</script>

How this would be implemented exactly will be up to you! I have (for examply) not idea how you have formatted your ID’s.

Cheers, Jory

• This reply was modified 6 months ago by Jory Hogeveen.

Hi @pixelhappystudio

Did you by any chance update to the latest Pods version? And if so, please check the new security updates since v3.1!

https://pods.io/2024/02/21/pods-3-1-feature-release-access-rights-revamp/

If that is not the case or isn’t helping at all, please review if there are other changes made. It might be a plugin conflict that occurred after an update.

Cheers, Jory

Hi @juchheim

/wp-json/pods/teacher is not an endpoint to fetch post data, it’s for the information about that particular Pod. To fetch posts you’ll need to use the WordPress core REST API.

The REST API is a WordPress core option, Pods optionally adds it’s fields to the results but cannot change in inner workings. Please refer to the WordPress core documentation.

Cheers, Jory

Hi @annagater

Did you by any chance update to the latest Pods version? And if so, please check the new security updates for forms and dynamic data since v3.1!

https://pods.io/2024/02/21/pods-3-1-feature-release-access-rights-revamp/

If that is not the case or isn’t helping at all, please review if there are other changes made. It might be a plugin conflict that occurred after an update.

Cheers, Jory

Hi @guiadm

Please give us more info about what you created exactly. Did you by accident create an Advanced Custom Type (ACT)?

Cheers, Jory