New Module: Structure - Uses entries to create a page hierarchy for static and listing pages

I am using structure 1.3 and have problems getting the {exp:weblog:prev_entry} tag to work in the same “order” as the “structure” order.

If I create a new page with structure and change the order the {exp:weblog:prev_entry} tag would not be synced because it sorts using the entry_id.

Example: page A, page B, page C are existing pages in structure. I add page D and place it on the first position. D A B C.

If I view page D the {exp:weblog:prev_entry} tag would give me only the prev link because its sorts it after entry_id. But it should show me the next link instead.

What would be the way to go to make structure play nicely with the {exp:weblog:prev_entry}? Changing the entry_id manually?

@Interfacer That tag does not work with our pagination currently as our pagination is somewhat custom. We have plans for rev + next soon, but it would require an upgrade to 2.0.

Thanks Travis, Is there a work around though. If I just change the entry id in EE so that the page D would be the first one? Not the prettiest idea but would work wouldn’t it.

@Interfacer I haven’t tested, but I don’t think that tag would register. If you think it might work, try it out until we can implement.

Hi,

Having an error issue with structure. Everything was going fine and now all of a sudden i am getting this error whenever i try to add a page.

“You are not authorized to post in this section”

The only thing i changed was i added a couple of custom fields to the section that most of structure is using. But i posted some pages after adding them without difficulty. Now i only have 1 page on the structure tab that it will let me add pages below without getting the error.

Odd thing is i can use the publish tab and then manually add the structure info of parent etc from the structure tab on the publish page and that works fine.

Has anyone else had this error or problem. I saw a bit in the thread but it was very old and didn’t seem related. I even went to the trouble of checking and resaving each entry.

@PhilBrienesse Is it a super admin account? If not, are you sure it has access to that weblog? Can you try adding another login and doing it through another user to see if that works?

Yes it is a superadmin and just for kicks i created another member group to see if that was the issue and still no go. As i mentioned i can post to this section using the regular publish tab.

Was this install moved from anywhere? Has anything in the DB been changed? It’s odd that it just stopped working, something had to have changed. Does removingg the new custom fields allow you to post?

Also just created another weblog and tried switching one of the problem pages to that and also did not work. Tried creating another top level page and i can add new sub level pages to that but if i move any of the current sub level pages into that top level I still get the same error from them.

Ok so i did some thinking and i think i installed reeposition around when it stopped working. Removed that plugin and still have the same problem. Removed the custom fields as well and still not working. I know it is extremely odd. I can add new top level pages manually and then add subpages in structure no problem. It is existing pages that are giving me the error. Worst case i guess i can delete all and start with fresh pages but i am loath to do that. Also pages that have listings attached to them can have listings added through structure as well? Very odd indeed. Unless you have any other ideas I will delete all the pages tomorrow and start fresh and see what happens.

@PhilBrienesse This is specific to your install and not anything we should clog the forum with. Please email answers to my above questions to support [at] buildwithstructure [dotcom] Thanks!

Is structure supposed to honor expiration dates? When i use

{exp:structure:nav_sub current_class="current" start_from="/projects" show_depth="2"}

I would expect that list not to include entries that have passed there expiration date yet it does. Am i just missing something?

Just for the heck of it i removed the show_depth and also tried adding show_expired=”no” but it made no difference. Any ideas here?

So fresh install of 1.6.8, module installed and semi working (more on that later) -just working through deleting some of my test entries prior to setting up and every entry I try and delete this warning pops up:

Error Number: 1064 Description: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ‘DIV 2) AS numChildren FROM exp_structure AS node INNER Query: SELECT node.*, (COUNT(parent.lft) - 2) AS depth, if((node.rgt - node.lft) = 1,1,0) AS isLeaf, ((node.rgt - node.lft - 1) DIV 2) AS numChildren FROM exp_structure AS node INNER JOIN exp_structure AS parent ON node.lft BETWEEN parent.lft AND parent.rgt WHERE node.entry_id = ‘4’ GROUP BY node.lft LIMIT 1

If I delete 1 by 1 I still get error but a simple “back” and “refresh” displays the entry has gone just wondering of this is a serious error or could be impeding the module at all?

Edit: Similar message when adding the “Page URL” within the structure tab of an entry and then trying to save :( Unfortunately the server is an IIS server but running PHP 5.2.2 and MySQL 5.0.27

@PhilBrienesse nav_sub does not work with expiration dates currently.

@Cheif Never seen that, did deleting entries ever work or is this new? Has something chaged?