Problem with custom taxonomy in custom post type

One needs to select the post type to query when creating an Archive template in Elementor Pro.

See https://elementor.com/help/create-archive-template/

Elementor does not follow most rules of WordPress templates. It creates its own system within WordPress.

Hi @pdclark, thanks for your reply. As I said in my question, I know how to create template with Elementor Pro, and it works fine with ACF+Elementor Pro, but as you see in the images I uploaded, when I create an archive page from CPT, each taxonomy in the URL ( example.com/writer1/ ), should display the list of all CPTs with the same taxonomies ( “writer1” ), but unfortunately it does not work with Pods+Elementor Pro as explained in my first question.

I can run some tests tomorrow, as there have been some historical complaints about Elementor detecting registered taxonomies, but here are some things to verify in the meantime, as Pods mostly provides a user interface to the core WordPress registration systems, so there is a good chance a checkbox is not aligned:

• Is “rewrite” checked under the Taxonomy Pod’s Advanced Options tab?
• In your screenshot of the post type Advanced Options tab, “Publically Queryable” is not checked. The description of this setting means that when not checked, it cannot be queried for archive pages. Does checking this box resolve it? Likewise, the description after that indicates the content is “Private”. This may also be an issue, depending on the capabilities of the viewing user account.
• After verifying and saving these options, does it change anything to save permalinks under Settings > Permalinks and clear any hosting caches?

Hi @pdclark, thank you very much, your explanation solved this issue.

Now that you are going to run some tests, please check why the “number” field and “currency” field is not displaying in Elementor dynamic tag.

https://ibb.co/7kyqVs6
https://ibb.co/PDSzvy1

Have a nice day!

The Pods integration written by the Elementor team is frequently reported as broken and incomplete in many ways.

The menu in the screenshot is written by the authors of Elementor.

As this is a frequent request, there are two solutions readily available from Pods:

The first solution is to use the Pods shortcode, either to display individual fields or Pods templates. This causes Pods to handle the rendering of the field, instead of the theme, and is compatible with any page builder module which supports shortcodes.

The second option is a paid add-on compatible with many page builders, including Elementor: it can be found by searching for Pods Pro by SKC Dev. This option implements all features found in the Pods blocks for the WordPress default block editor within the context of most page builders, such as Elementor.

If you have problems with Elementor at that level, it’s best to check with Elementor Pro support there since that’s a paid feature I believe on their side.

And like Paul mentioned, there’s also the Pods add-on that I personally built as the lead dev of Pods itself. It offers a bit more flexibility in some areas and I’m working on implementing new Pods dynamic tags since Elementor pushed Custom Fields into the higher price levels of Elementor Pro.

https://pods-pro.skc.dev/downloads/page-builder-toolkit/