Problem:
The user is using the same archive template for the custom post type and certain taxonomies. He uses two views he would like to use inside of the archive template and display one of them for post type archive page and the other for the taxonomy archive pages.
Solution:
This can be implemented using the Conditional block, but you will need to create, and register, a custom function to be used inside the conditional block. Check the article below
The function can use WordPress core functions to check if the current page is the post type archive or the taxonomy archive.
Problem:
The user is using a lazy loading plugin to optimize the loading of images, he needs to add a specific class to the tag generated by the Image block.
The classes added to the image block settings are added in the
tag that wraps the tag.
Solution:
We can work around this using custom code:
Links in URL custom field gets appended to site url when clicked rather than going to the URL that is stored in the field.
Example when google.com is entered into the url field it gives the below on the frontend
mysite.com/google.com
Solution:
This is happens because you are adding the URL to a url field without adding http:// before the actual URL.
You will need to edit your fields to include the http:// to resolve the issue. Secondly I would recommend enabling the field validation for this In your field settings at Toolset -> Custom fields.
This will ensure that only valid URL's are added to the field and prevent this from happening in the future.
Problem: When the plugin WP Login Form is active, custom search Views are not working as expected if the filters and results are displayed separately via separate shortcodes or widgets.
Solution: Update the wp-login-form plugin to get the latest version, which includes a fix for this problem.
