Skip Navigation

[Resolved] wpv-header in taxonomy

This support ticket is created 7 years, 4 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

Tagged: 

This topic contains 8 replies, has 2 voices.

Last updated by Bochnacki 7 years, 3 months ago.

Assisted by: Luo Yang.

Author
Posts
#551120

Wpv-header works when:

<body class="archive post-type-archive post-type-archive-osobowy logged-in osobowy-mercedes-glc hfeed">

But it does not work when:

<body class="archive tax-osobowe term-audi term-5 logged-in osobowy-audi-q3 hfeed">

I do not know if I am explaining the problem well.
I have created an archive. The crumbs look like this:
Here "Home -> Osobowe -> Audi" wpv-header works.
Here "Home -> Osobowe -> Audi" wpv-header does not work.

Please help me.

#551205

Dear Bochnacki,

Are we talking about Views CSS class name "wpv-header-asc" and "wpv-header-desc"?

The CSS class "wpv-header-asc" and "wpv-header-desc" should be able to take effect in the taxonomy archive page too, please check these:
1) deactivate other plugins and switch to wordpress default theme, and test again
2) If the problem persists, please point out the problem page URL, where and how can I see the problem, thanks

#551235
wpv-header.jpg

"Are we talking about Views CSS class name "wpv-header-asc" and "wpv-header-desc"?" - Yes exactly.
I deactivated other plugins and turned on the default theme of wordpress - nothing has changed, the problem is still.

For now, the problem can only be seen on one example: hidden link
Here hidden link is good
Here hidden link not working anymore.

#551264

I have changed a computer, Please provide the credentials of your website in below private message box, I need to check your website settings, thanks

#551277

Thanks for the details, I am checking it in your website, will feedback if there is anything found.

#551885

I assume we are talking about the text string T"Data dodania Cena Przebieg"
in problem page:
hidden link

Above page is a taxonomy page, you setup it with a Views wordpress archive
hidden link
Section "Loop Output Editor", With the shortcodes [wpv-heading ...]:

    [wpv-heading name="post-date"]Data dodania[/wpv-heading]
    [wpv-heading name="types-field-cena"]Cena[/wpv-heading]
    [wpv-heading name="types-field-przebieg"]Przebieg[/wpv-heading]

But the shortcode [wpv-heading] does not work in wordpress archive view, it works only in the normal view.
page hidden link
is using a normal view:
hidden link

In your case, I suggest follow our document to setup the "sortby"
Allowing visitors to sort the front-end results
https://toolset.com/documentation/user-guides/allowing-visitors-to-sort-the-front-end-results/

#551951

I applied the sort that you advised.
My test server is not a speed daemon but using this sort of page reloads 20-30 seconds... And currently I have only two test items in the list. It is not acceptable.
Why is this happening? Can somehow improve it?

I understand that in my case this is the only solution?

#551978

The performance problem should not be related with the [wpv-sort-orderby] shortcode, you can edit the archive view "Osobowe":
hidden link
in section "Filter Editor", find and remove the radio sortby field:
[wpv-sort-orderby ...]

and test again in the front-end, the performance problem still persists, so it might be other problem/conflict, please create new thread for new problem, thanks

#553783

The problem is already outdated. I use parent-child relationships. The views of taxonomy will not be used at all.
Luo, thanks for the tips and help.