Forum Replies Created
-
Posts
-
Hi,
1. You can actually turn that off here. It was added because some users wanted to make redirections from empty tag permalinks to different pages. It was requested many times, so we added it as a feature.
The archive page breadcrumb and layout is controlled by the theme. All the plugin does in this case is display the “marci” tag and the link to that archive page, which is requested from WordPress core. There is probably a way to change that text somewhere in the theme settings, usually most modern themes have a customizer feature where you can change the archive breadcrumbs and the text as well.
2. I just logged in to check, it seems to be working all right on my end. I only see the tagged posts in the results, for example: https://i.imgur.com/mehGTNV.png
Sure!
I tried that, but it looks okay on my end. I’m getting products first, then recipes (or similar) then blog, picture 1 then scroll down.
Hi,
You can try utilizing the post type ordering feature here: https://i.imgur.com/yJtQwwD.png
That will try to push the results according to the post type list specified, so certain post types will be preceeding others.Hi,
Thank you very much for the details.
It was seemingly only a corrupted stylesheet file. I have re-saved the compatibility settings without changing anything and it solved the issue (by regenerating the styles). It should be okay now.
Hi,
You are welcome!
1. I’m afraid not in an inline position. You could use the search and the settings shortcode separately side-by-side in a two row container, but that would not have the same effect.
2. You can change it here: https://i.imgur.com/8ocKiVB.png
Hi,
1. It is by design as empty tags would not return anything. The only way to change that is by editing the code. I can take a look if you want and let you know, there might be a hook or similar, but I’m not a 100% sure.
2. The most likely cause can be taxonomy term inclusions. Can you check if you have anything enabled in that area? Those override the filters, so it could explain the issue.
Hi,
I’m afraid that is not possible. It is not a plugin limitation as taxonomy terms and term relationships are not shared across the multisite network, each subsite has it’s own and even if they had the same names they would not work as they are referenced by objec IDs.
Custom fields however may work, as those are stored by name and not by ID, and the names can be the same.
