Thread

Hi there,

I’m having two problems with the Pages module, one more pressing than the other.

1) The less pressing issue involves trying to remove a Page URI from within the weblog entry. I’ll remove the text in the “Pages URI” field, click “Update,” but the “Pages URI” is still there when I open the entry again. My workaround has been to go to the Pages module configuration and check the “Delete” box, and delete it that way. That had worked just fine until this morning.

2) When I tried to delete a page URI using the checkbox on the Pages page, i got a bunch of PHP/MySQL errors and warnings:

Notice: Undefined index: uris in /FILEPATH/modules/pages/mcp.pages.php on line 515

Warning: Invalid argument supplied for foreach() in /FILEPATH/modules/pages/mcp.pages.php on line 515

Warning: natcasesort() [function.natcasesort]: The argument should be an array in /FILEPATH/modules/pages/mcp.pages.php on line 143

Warning: Invalid argument supplied for foreach() in /FILEPATH/modules/pages/mcp.pages.php on line 170

I’m running 1.6.9, Build:  20100415. (Removed file path to my system folder and replaced with “FILEPATH”).

Since posting this morning, I’ve updated to the latest build, 20100430, with the same issue persisting.

Please advise.

Hi Douglas,

I believe I’m seeing this on my build as well. Can you confirm that after you attempt to delete one of your Pages from CP Home ›  Modules ›  Pages, you see the message “No Pages Currently Exist” even if there were other Pages left, and that the selected Page was not deleted?

Yes, actually, that’s exactly what happens.

And if I click on my “Pages” tab, the list of pages loads again (as opposed to saying “No pages currently exist” again), and that list includes the page I was expecting to delete.

Douglas,

I can also replicate this. Can you go ahead and report this in our Bug Tracker please? Please link to this thread as reference when doing so. Thank you.

Hi John,

The bug tracker does not allow me to select 1.6.9 as a version option.

Should I fill out the bug report anyway? Seems like it’ll get lost.

Douglas, here’s the right link for EE1.6.x’s bug tracker: http://expressionengine.com/bug_tracker/

The one John gave was for the 2.x bug tracker.

Great, thanks Sue.

Bug report submitted.

Here’s the link back.

https://support.ellislab.com/bugs/detail/12402/

You’ll now receive an update when there is a change made to the bug report.

Is there any chance this bug is going to get fixed in the next release? It’s been sitting with with a status of “New” since the beginning of May.

I am afraid we don’t have completion date estimates for the various bugs. Our devs are aware of the list and continue to stamp out the remaining bugs as fast as possible.