Click here to register or to donate.Auto self-registration is not available here - far too many spammers. This forum has many, many backlinks and because of that there is an intense desire among spammers to drop their links here.

[SOLVED] Issue with Hierarchical Pages plugin

#1

Oct 27, 2013, 06:23 AM

RHCdG

170 posts · Nov 2009

Netherlands

Hi,

As of recently, whenever I click on a menu item (page) in any of the menu widgets that I have, the child and parent pages open not only within that menu widget (which is what they should do) but in all menu widgets. I disabled all plugins but that did not help. I know I tinkered with the PageNavi plugin but I deleted that one altogether. Other than that I don't remember doing anything major except for upgrading to the new WP version, 3.7.

I left a support request on the plugin support page but have not received a response. I know this is is not an Atahualpa problem per se but you guys always provide such great support; would you care to take a quick look, and click on any of the menu items in the left hand bar (skip the top two as they don't have child pages)? The address is http://www.cornetsdegroot.com/
I appreciate!

Best,
Rutger

#2

Oct 27, 2013, 07:24 AM

juggledad

23,728 posts · Mar 2009

OSX 10.11.5 WP 4.x Atahualpa(all) Safari, Firefox, Chrome

what is the exact item to click on? I don't quite understand the issue. When I click on say 'De kunst van het falen (’78)' only it shows with children

Now, if you look under the other menu widgets, you will see that these 6 children are displayed at the bottom of all menu widgets. That should not be, and it never was; they should only open below the respective parent page in the respective menu widget...

Thanks, I knew I could count on your help!

#4

Oct 27, 2013, 07:54 AM

juggledad

23,728 posts · Mar 2009

OSX 10.11.5 WP 4.x Atahualpa(all) Safari, Firefox, Chrome

Ah, now I see. I didn't notice they weren't indented.

I'm sure this is going to be another WordPress 3.7 bug (excluding menu items from a category menu doesn't work because of a WP 3.7 bug)

What menu widget are you using?
(note: I am going out on a date day with the wife so it will be a number of hours before i reply)

The top menu widget (this is all regardig the left hand menu bar only) is Menu 1 (Page Menu), the widget below that is just Links, and all the other ones are from the Hierarchical Pages plugin. Does that help? And can I downgrade without losing any settings, and would that recover the issue for now?
Hope you had a good Sunday, I had one myself!

#6

Oct 27, 2013, 02:16 PM

juggledad

23,728 posts · Mar 2009

OSX 10.11.5 WP 4.x Atahualpa(all) Safari, Firefox, Chrome

You can downgrade as long as you did a database backup before you installed P 3.7...you did do a backup right?

You would restore your database and get a copy of WP 3.6.1 and manually replace everything in the WP folder EXCEPT for wp-contents and wp-config.php

The Hierarchical Pages Widget plugin only states it is compatible up to 3.4.2 so that might be the problem. In my test using two 'custom menu' widgets, I see no problem.

You are going to have to
1) wait till the plugin author fixes it or
2) revert to 3.6.1 or
3) find a different plugin

The setup is the same for all of them, the way I described in my previous response, except for the Sort Field, which is sometimes 'menu_order', or 'ID', or 'post_title'.

The top two widgets (START and CONTACT/VOLGEN) are not Hierarchical Pages widgets.

#15

Oct 28, 2013, 03:50 PM

RHCdG

170 posts · Nov 2009

Netherlands

I just realized that you don't know this plugin, so have no clue what I am talking about, sorry about that!
I just took a screenshot, you can view the widget right here.

#16

Oct 28, 2013, 05:03 PM

juggledad

23,728 posts · Mar 2009

OSX 10.11.5 WP 4.x Atahualpa(all) Safari, Firefox, Chrome

Ok, I took some time and looked at this. It seems to me that this plugin was never intended to be used multiple times. Having it multiple times seems to introduce bug where it always displays the children of the current page.

It would probably take me several hours to review the code and figure out where the issue is.

If the author doesn't get back to you you might want to look at just creating a set of custom menu's

Re: "Having it multiple times seems to introduce bug where it always displays the children of the current page."

But this is exactly the idea of the plugin. And until last week, it worked fine. The problem is that it opens child pages in ALL of the menu widgets instead of in just the respective menu widget, i.e. the one that holds the parent page the user has clicked on.

I could create multiple custom menus but I don't think they would offer similar functionality, i.e. have child pages displayed in the respective menu upon opening their parent page. Or, would you have suggestions for me? I would appreciate, and I will let you go with thanks for all the effort you put into this.

#18

Oct 28, 2013, 08:24 PM

juggledad

23,728 posts · Mar 2009

OSX 10.11.5 WP 4.x Atahualpa(all) Safari, Firefox, Chrome

Like I said before, there may be a bug in WordPress. The plugin is using the same wordpress function that is causing problem when passed the 'exclude' option. In this case it is being passed the 'include' option. So maybe there is a tie in, but I don't know enough about what the function is doing to be sure.

Hi again JD,
Just to follow up, I received a reply from the plugin author. He refers to this bug ticket, and advises that I either wait for a patch to 3.7 or to downgrade to 3.6.

Can I just ask you how long it usually takes before these patches are adopted?
The weird thing is I just uploaded so much stuff (mostly image galleries) to that website following the days of the upgrade to 3.7. It would otherwise have been no problem to downgrade. Or is there a way to save those new image gallery pages I created separately, downgrade to 3.6, and reupload the backup of those individual image gallery pages?

#20

Oct 29, 2013, 03:39 PM

juggledad

23,728 posts · Mar 2009

OSX 10.11.5 WP 4.x Atahualpa(all) Safari, Firefox, Chrome

That is the same bug I gave you the patch for and the patch does nothing as you have seen for yourself. You might want to let the plugin author know that.