Tome vs EE 1.6 Pages
Development and Programming
Hi Mark, congratulations on getting your old Pages module brought in as a first-party module in EE 1.6 … It has been mentioned that the new EE Pages module does not have all of the functionality of Tome - What exactly are its shortcomings?
I’m about to start developing a new site which will mostly be static pages - Should I install Tome or can the EE Pages module do the job of spitting out navigation lists/sitemaps/breadcrumbs based on my site structure??
I was having some good success with the following method using your old Pages module:
<ul id="topNav">
{exp:static_page_path direction="post" page="0" depth="1" nest="false"}
<li id="{short_name}"><a href="http://{url_title}">{title}</a></li>
{/exp:static_page_path}
</ul>(and something similar for a left-nav.)
- anyone know if the new EE 1.6 Pages module can do this?
I would not consider this “a module brought in as a first-party module”. The core functionality may be the same, but it’s been completely redeveloped by EllisLab, far as I can tell. It works somewhat differently, too. My advice: Use the built-in module until you run into limitations, than research other options. It is my understanding that Tome will be fading out as Pages progresses.
Any idea on when the next update for the Pages module will be? I’d like to see the same functionality built into Pages as Tome so its easy for my clients to update content.
![[ Rrr Pro*]'s avatar](https://pagingstaging.expressionengine.com/asset/images/avatars/avatar_46875.jpg){kind=avatar}
Any idea on when the next update for the Pages module will be? I’d like to see the same functionality built into Pages as Tome so its easy for my clients to update content.
Same here!