Adding property set to page.nav (getPage)

Hi,

I’ve recently begun using ModX and have taken it upon myself to build a blog using the guide over in the documentation. This was all going well, until I decided I wanted to change the pagination outputs (from page numbers, <<, >>, first, last to older, newer only ) So I assumed adding a property set would be the sensible thing.



After this assuming I would add it as usual I appended @new (the property set name) to the [!+page.nav]
This didn’t change the affect.

I then found online a suggestion to use [!getPage@new] before the [!+page.nav] but again no change.

I have cleared cache etc. and can’t think of anything else I’ve missed.

Suggestions or solutions would be great. Apologies if I’m missing something super simple.

Mark

Update:

As a semi-solution (I’d still prefer to use a property set)...

I’ve edited the snippet so that it no longer replaces the properties if they are empty, but replaces them anyway (It doesn’t seem to be calling in the properties however I set them elsewhere)

However (Separate issue, apologies) I can’t use empty values to replace properties within the snippet. If I do this, it fails to add the pagination to the page.

(ie $properties[’pageNavTpl’] = ($pageNavTpl) ? ’’ : $pageNavTpl; stops the content from being added to the page.)

Any solutions to either issue I’d prefer not to use ’&nbsp;’

Thanks

Have u tried putting that tpl in the chunk and then adding chunk name in the property set?

Apologies, I’m not quite sure what you mean

Put the <li>.....</li> html template code in the chunk, and use the chunk’s name without [[$..]] eg. mychunk in the property set.

Zi, that won’t work here. There is a pull request waiting to be merged that fixes the issue with not allowing empty values in those properties. I will get it merged in and release a new version shortly.

Thanks Jason.

@renniks: You heard the man!