How to create / edit page hierarchies in 2.0?

[geotek]

How can we create / move content pages below top level if the "parent" field is missing in content manager?



I checked different browsers and two different 2.0 installations (one fresh installation, one migrated website - the parent field is always missing, during page creation and when editing. I also found no way to rearrange page hierarchy via GUI and the documentation was not helpful here. Logged in as admin, just in case this is a permission issue.

Please advise

[calguy1000]

The only way that that would happen is if you either have absolutely no content pages (don't even think that that would happen then) or you have some browser plugin that is messing with the javascript.

Please check for javascript errors,

[geotek]

I do have content pages on both installations (on the fresh installation your demo content, on the second site an upgraded website with real content, both are working fine)

If I try to edit a subpage of the demo site that already has a parent page, the parent field is also invisible.

There are a bunch of Javascript warnings but no errors.

I tested it with Firefox, Chrome and Maxthon Browsers (both of the latter without any plugins) and all show the same effect.

In firebug I can see that the parent input field is set to "hidden":

Code: Select all

<p class="pageinput">
<input id="cms_hierdropdown1" class="cms_hierdropdown" type="text" maxlength="50" size="50" value="-1" title="This field displays the selected content page. The actual string displayed (page title or menu text) is dependent on user and site preference." readonly="readonly" style="display: none;">
<input type="hidden" value="-1" name="parent_id">
<__script__ type="text/javascript">
$(function(){ $('#cms_hierdropdown1').hierselector({current: 33,parent: -1,allowcurrent: false,use_perms: true,ignore_current: false,allow_all: true,use_name: true}) });
</__script>
</p>

Removing the hidden attribute in Firebug makes the input field temporarily visible. It shows the correct content id of the parent page.

By the way - seeing an input field instead of a dropdown list makes me wonder: Does this mean that in in V.2.0 we have lost the ability to quickly choose the parent page from a dropdown-list of existing page names as it was in V.1.x and are now forced to blindly enter the ID of the parent page? This would be a step back in useability IMO.

[aviapic]

checked on several browsers with cmsms 2.0 installation - the parent field is always visible.
tested on opera 31.0, Firefox 40.0.3, IE11 (no problem).

maybe you can try system maintenance to update page hierarchy positions and check database status.

[velden]

By the way - seeing an input field instead of a dropdown list makes me wonder: Does this mean that in in V.2.0 we have lost the ability to quickly choose the parent page from a dropdown-list of existing page names as it was in V.1.x and are now forced to blindly enter the ID of the parent page? This would be a step back in useability IMO.

The input field itself is hidden because some js makes it a fancy dropdown box.

Tested with default sample content in Firefox and just works for me.

[geotek]

@velden: glad to hear that there should be a dropdown box.

I just dumped all files and db tables and reinstalled 2.0 from scratch. (The 2.0 installation wizard is fantastic, by the way) - All dependencies were met, no errors whatsoever, but same situation: Demo content works fine but still no parent page selection. Tested on yet another FF 40.0.3 and MS Edge browsers without any extensions. Host server is up-to-date OpenSuse 13.2.

Looks like there is something seriously wrong.

if you want to have a look for yourself I can mail the admin credentials. It is just a demo/reference installation, so you may freely change things.

[calguy1000]

if you want to have a look for yourself I can mail the admin credentials. It is just a demo/reference installation, so you may freely change things.

If you also have ssh access so that I can debug things I will take you up on that offer.

Please PM me.

[geotek]

This issue was resolved in V.2.0.1 )