Pagination links broken
Development and Programming
But I’d suggest (based on teaching many, many people EE) if you are still thinking of your site in terms of having to build “pages” and then worry about how to build navigation to those pages you haven’t fully grokked EE yet. EE is a post (or entry) based CMS, not a “page-based hierarchical” CMS. This is a paradigm shift that can be hard to get your head around if you’ve used other page-based, hierarchical CMS.
I’m sorry as this is off topic but Boyink! that’s just plain crazy talk. I agree that one of EE’s core strengths is that it is entry based but completely shunting the idea of pages is ridiculous. The perfect balance (imo) is using Pages and Posts in harmony together, using whichever makes more sense in each particular context. This is one thing Wordpress does really well with it’s “paradigm” of Posts + Pages.
I could run through plenty of client sites where it made sense to use pages and other projects where entries made more sense, but to tell someone that they don’t “get” EE because they want to use Pages is completely wrong and irresponsible. Anyway, back to the topic at hand!
@jwindhorst
if your ‘static’ gallery introduction at the top of your template is serving up multiple ‘pages’, then yes you appear to be mistaking what you can do with the pages module. You can’t mix like that because as soon as a pages module uri is ‘broken’ it’ll fall back to a native way of trying to parse the url.
There are several ways of doing what it is you’re trying to do, in this case I think you’ve chosen a route that I think has more issues than it’s worth.
I can’t really follow why you’d be using php like you have, it seems odd to me but I’m sure you’ve got your reasons.
Iain
@iain
What part of my PHP don’t you understand? I’m basically just doing string manipulations to go from the thumbnail name to the full size image name. It’s entirely inconsequential to how the page loads. Were using a lightbox so I needed to get the full image name in the same template as the thumbs.
So if I am using the pages module wrong, it is merely me being a n00b to EE2. All I really want to do is get pagination working. I could most likely roll my own, or go with matrix which does look like it might work for my situation, but I need to make the decision soon as I have the marketing department waiting to add content even now.
What I found odd about your code is that you’re defining an $entry_id variable in your ‘intro’ channel entries call, then hiding the entire output of the gallery if $entry_id doesn’t match what appears to be a custom field called ‘gallery’.
If I read your code right, this is what you’re doing right?
{channel:entries}
$entry_id = {entry_id}
{/channel:entries}
{channel:entries}
{if $entry_id = gallery}
show the gallery
{/if}
{/channel:entries}Seems odd, that’s all - but like I said, I’m sure you’ve got your reasons.
btw, the pagination code is inserted by EE sometimes in places where you would not expect. Instead of doing this:
<div id="paging-wrapper">
{paginate}
{pagination_links}
{/paginate}
</div>I’d recommend you do this:
{paginate}
<div id="paging-wrapper">
{pagination_links}
</div>
{/paginate}Also, just bear in mind if you are using matrix there are limits on the number of rows you can have (which are not fixed). Things start coming into play like server memory and your client’s browser of choice for example. (IE is painfully slow rendering a large matrix). I’ve read folks hitting problems between 30 and 50 rows, probably worth noting if you’re going down that route.