- This topic has 23 replies, 3 voices, and was last updated 1 year, 10 months ago by Tom.
July 26, 2019 at 4:44 am #967723retroreiz
currently I have the problem that the price filter destroys the header area.
Other filter properties do not destroy the design, only after price filters caused the problem.
I strongly assume that the filter plugin causes this problem.
How can I tell the header in the element area of GeneratePress that if price is being filtered, then does the normal header area have to be taken?
Thank you in advance. Greetings AndreasJuly 26, 2019 at 8:24 am #967962LeoStaffCustomer SupportJuly 27, 2019 at 7:12 am #968543retroreiz
Sorry for the misunderstanding. I’ll try to explain it again.
This is what it should look like when you filter for something (right):
So it looks like if you filter for a price (wrong):
Basically, the filter function works correctly. The header looks right on all pages. However, only if i filter for the price, the header image is swallowed.
I hope so it is better to understand what I mean.
AndreasJuly 27, 2019 at 9:49 am #968748LeoStaffCustomer SupportJuly 28, 2019 at 11:02 pm #969736retroreizJuly 29, 2019 at 8:28 am #970218LeoStaffCustomer SupportJuly 31, 2019 at 12:04 am #971781retroreiz
I’ve tried everything now. Also on Entire site, but that did not bring any improvement. As if there would not be this page and he does not know what kind of header to use.
I have a test installation. Do you want to look at it, maybe I missed something?
Greetings and Thanks, AndreasJuly 31, 2019 at 9:08 am #972309TomLead DeveloperLead Developer
Access to a staging/test installation would be great! It looks like the Element doesn’t know if it should display when those filters are active.
You can send login details through our Account Issue form: https://generatepress.com/contactJuly 31, 2019 at 10:30 am #972389retroreiz
i send you the login details for the staging installation.
Thank you 🙂
Greetings, AndreasJuly 31, 2019 at 4:37 pm #972584TomLead DeveloperLead Developer
I just tried to replicate this on my install, but it works as it should. Can you try:
1. Disable all of your other Header Elements. Any change?
2. If not, disable all of your other plugins. Any change?
3. If not, can you install Query Monitor and let me know?: https://wordpress.org/plugins/query-monitor/
Thanks!July 31, 2019 at 11:16 pm #972707retroreiz
1. If I disable all elements and leave only one, then there is no difference. If I delete all elements then the header is white over all this, but that’s probably normal.
2. If I deactivate the filter plugin of xforwoocommerce, then it works with the header again. Apparently the plugin expects a different header.
3. I have installed the “Query Monitor” plugin. Unfortunately I do not see where the problem is.
I hope you can help me with this somehow.
Greetings, AndreasJuly 31, 2019 at 11:31 pm #972718retroreiz
i look at the monitoring, and the only change then i aktivate the filter plugin, it at the request.
The header don´t work and filter plugin activate: https://ibb.co/SB1qwgS
The header work and the filter plugin deactivate: https://ibb.co/drFWdj5
Can you see anything wrong in the request?
Greetings, AndreasAugust 1, 2019 at 9:16 am #973190TomLead DeveloperLead Developer
So this plugin is causing it?: https://codecanyon.net/item/xforwoocommerce/23673114
What are you using it for?August 2, 2019 at 8:25 am #974057retroreiz
i using the filtering function, badgets and product options function.
https://ibb.co/RjgTy1n – filter
https://ibb.co/b7pH7M2 – badgets and product options
https://ibb.co/TwhN1XB – the three plugins are activate
I know if I deactivate the filter plugin, the problem disappears. The other plugins do not cause the problem of xforcommerce.
Greetings, AndreasAugust 2, 2019 at 6:17 pm #974421TomLead DeveloperLead Developer
Is it a specific feature in that plugin which is conflicting, or is it just the fact that it’s activated (even without using any of the features)?
Just trying to get an idea of how it could be conflicting. It seems like the plugin is tricking WordPress into thinking we’re no longer on the product archive page once the filter is used. It’s possible that it’s a bug directly inside that plugin.
- You must be logged in to reply to this topic.