Pages Bug Thread
Development and Programming
The Pages module has grown immensely popular over the past year, something that I never could have guessed or planned for. I’m humbled by everyones gracious comments on how the module has eased their development and made training clients a breeze.
Of course nothing is without it’s faults, this module included. It has seen it’s growing pains (some would probably argue is still having them) and as the term implies it has grown with them. With each bug you reported the module got a little bit stronger. You reach a point though when bugs and features start to blur together. I am of the opinion that we are at that point now. The current twenty-seven page thread announcing the module is littered with bugs/features/complaints/successes/etc… In order to simplify this and hopefully remedy some confusion people have had with the module I’ve worked with the magnificent Derek Jones to close the old thread and start anew here.
Now before you go posting, there’s one important thing you should know. With version 3.6.0 I have officially ended development on the 3.x version. I’ve started over for 4.0 and rebuilt the module from the ground up with all your improvements in mind. The code should be leaner, faster, and a whole lot more error proof. I’m also not planning on implementing many new features for 4.0. I’d like to take what we’ve go going with the 3.x version and just rework that into a 4.0. Before anyone asks, “When’s 4.0 coming?” let me answer with “Eventually.” That means that I’m working on it in my spare time around client work and when I think the module/extension/documentation is in a good spot I’ll release it. I’m hoping to do that within a few months time.
So, what I’d like to do with this thread is close it off to any feature requests or general use questions. If needed someone can start a new thread for feature requests and questions can each take their own thread. This thread should be used only to report bugs in the current release (3.6.0). Something along the lines of “doing x makes y not work.”
Finally, if you’re looking for support, try the following before posting your requests as a new thread:
I’ve finally wrapped my head around what the Pages module does (mostly). But I’m having a problem with second level (child) categories displaying content.
I can create content for the categories and child categories without a problem. Also, I can navigate the static pages using the Pages Main Screen. But when I click on View for child categories, the page is styled but there’s no content.
Some lo-fi examples:
Books (mysite.com/books/) <–works fine – Fiction (mysite.com/books/fiction/) <–no content
Movies (mysite.com/movies/) <–works fine – Drama (mysite.com/movies/drama/) <–no content – Comedy (mysite.com/movies/comedy/) <–no content
Anyone have an idea of what I may be missing?
Hmm… I expected a response by now.
As I stated, first level categories work with the static pages module. But for some reason, second level categories do not show corresponding category content.
Here’s a snippet of the template code I’m using:
{assign_variable:my_weblog="main"}
{assign_variable:my_template_group="static"}
{head}
<body id="{static_page_name}">
{header}
{nav}
{column-left}
<div id="column-main">
{exp:weblog:entries category="{static_page}" disable="member_data|comments|trackbacks"}
{body}
{extended}
{/exp:weblog:entries}
{mission}
</div>
{column-right}
{body_close}I’m probably making an obvious mistake in setting up the module. But I haven’t been able to find it. I hate to have to scrap the Pages Module but if I can’t get subcategories to work I’ll have no choice.
j.brotherlove, I have merged your post with the one Mark created for support of this module.
thanks derek.
j.brotherlove - everything looks accurate. you may want to try adding the dynamic="off" parameter to the weblog entries tag and see if that helps.
Thanks Mark.
It was indeed the dynamic="off" parameter that I was missing. I added it and all is well. I’m familiar with embedding weblogs and using “dynamic off” but when content displayed for parent categories I was thrown off track.
Thankfully, I stumbled upon the solution in the wiki (which I highly recommend) sometime in the twilight hours. Pulling an all-nighter and coding EE templates is probably not a smart idea.
😝
Sorry I missed your thread the first time around, it didn’t get caught in my newsreader for some reason. Anyway, i’m glad it’s figured out.
Hey Mark. Very nice mod here, thank you thank you.
I’m not sure how big an issue it is or if I’m missing where to set this, but I made a new install, installed your mod, created my pages weblog, setup my categories in their structure but i gave them each a short description(in the back of my mind I was going to use this for meta data). I then added a new tab for the modele and I was pleased to see the hierarchy I had just setup appear like magic. Man that’s nice.
I entered my content into the pages, then clicked view. I noticed the url’s where using my categories descriptions instead of the actual category name, so the url was getting written with spaces and my short description. Is that a mod bug or is that something I can change?
I did go back and remove the category descriptions and that defaulted back to the category name in the url.
we’ll originally it was a ‘feature’, so that if you wanted your url to be different from your title, or different than what I said it should simplify to you can place your ‘url_title’ into the cat description and Pages will use that.
Hi Mark,
First, thanks for creating the Pages Module/Extension. The site-map view provided via the Pages tab will be a big help for my clients. Helps my brain too. I’m currently using the module on three sites, and all appears well at this point except for one thing.
In a post on the main thread about the Pages Module (http://ellislab.com/forums/viewreply/182396/), you’d mentioned “Finally, if you choose to install the extension it will remove the “Content Pages” weblog from the publish menu so your client doesn’t get confused and ask “Why don’t we publish to this one?””
I have not been able to get this to work on any of the sites; i.e., my Static Pages weblog always shows as an option under the Publish menu. I’ve double checked that the actual Pages Extension is enabled (and not just extensions in general from the top tab). Am I missing something?
I have v.3.5.9 installed, and thought I’d read (and actually used) a little icon that appeared when an upgrade for the module was ready. But it still says v.3.5.9 on the Modules page list. Maybe I’m hallucinating? If the auto update icon is not there, should I just FTP the 3.6.0 files over or uninstall 3.5.9, FTP 3.6 over and reinstall? I don’t want to hose the Pages/Category structure. (BTW, for what it’s worth, in looking thru the files to see what version I really had, I noticed in the 3.6 version of pi.static_page_path.php & pi.pages_results.php that pi_version in the $plugin_info array was set to 3.5.8. My 3.5.9 install on the server has 3.5.9 for those values.)
Thanks!
Paula
Hello - I have spent time going through most of the posts on this thread and the earlier one. At first i thought that it might offer a solution for building an easier EE site. Then after digesting for awhile I am wondering exactly what would i gain from using the pages modules? For example it is said that using static pages to have a site such as:
Books (mysite.com/books/)
– Fiction (mysite.com/books/fiction/)
Movies (mysite.com/movies/)
– Drama (mysite.com/movies/drama/)
– Comedy (mysite.com/movies/comedy/)
is easy as each page can be updated directly.
But could I not accomplish the same thing by creating two weblogs: Book & Movies and have for each categories such as Fiction, Biography and Drama & Comedy? f
What is the main advantage of using pages vs the default EE install?? (p.s. can someone provide an example of a website or two that was done in pages modules? And if one installs the PagesModules how easy is it to update EE without also having to update the pages install …) thanks! cheers….
What is the main advantage of using pages vs the default EE install??
I’m not an expert, but the advantage of the pages module is that it gives you the ability to edit the pages in a hierachial view rather than clicking edit then sorting through posts. It uses categories within one weblog to create the hiearchy and you’ll create one post to each category to represent a single page. There is also the dynamic page capability so in your view you can set for example “news” as dynamic and point it to a different weblog.
Secondly, it can all be done with out the static pages module, but if you have a client editing the site the module makes it easier for them to understand especially if they are coming from different cms where static pages are separate from dynamic content e.g. Joomla!, Wordpress, Typo3 and others.
It just another way of looking at weblogs.
This is not a bug, but definitely a feature that I think would be helpful. When automatically generating the navigation using static_pages_path, is there a way to exclude a page?
Not sure if this is a bug, is not supported, or a coding error on my part but…
Should I be able to use the status parameter with the static_page_path plugin? I’m using ‘static pages’ to define my site structure, and the static_page_path for my main menu. However, when I set the status to ‘closed’ for one of my pages, the page is hidden on the front end, but the menu link is still visible.
My top level menu links are hard coded and am using the following code for the submenus:
{exp:static_page_path direction="post" page="4" nest="false" depth="1"}
<li><a href="http://{url_title}">{title}</a></li>
{/exp:static_page_path}So… would it be possible to add status=”open” somewhere?
Tx in advance.
Hi there,
I’ve just installed the the Static Pages module, v3.6, and the latest version of EE, and I’m having a few problems that I wonder if someone could help me with.
The following code shows all entries in the ‘Content Pages’ weblog:
{exp:weblog:entries}
<h1>{content_body}</h1>
{content_date}
{/exp:weblog:entries}Yet the following code displays nothing - can someone help correct this code please? I’m trying to display the ‘About Us’ category in the ‘Content Pages’ weblog (note that this is only a test EE install as I’m learning, so is also my first and only weblog).
{exp:weblog:entries category="About Us"}
<h1>{content_body}</h1>
{content_date}
{/exp:weblog:entries}Thanks for any help,
Ste