Newer and older tags not accepting class or html_id

sambooth74 · 2021-02-21 17:49:59

Hi,

I’m using the newer and older tags but I can’t get the class or html_id to work.

Here’s my code:

<txp:evaluate test="newer,older">
	<nav class="sb74-pagination" aria-label="<txp:text item="page_nav" />">
		<txp:newer rel="prev" class="sb74-button">
			<txp:text item="newer" />
		</txp:newer>
		<txp:older rel="next" class="sb74-button">
			<txp:text item="older" />
		</txp:older>
	</nav>
</txp:evaluate>

Here’s the HTML output:

<nav class="sb74-pagination" aria-label="Page navigation">
	<a rel="prev" href="https://sb74.net/preview/">
		Newer
	</a>
	<a rel="next" href="https://sb74.net/preview/?pg=3">
		Older
	</a>
</nav>

As you can see, the class is not being applied to the newer and older links.

Am I doing something wrong? Many thanks in advance.

colak · 2021-02-22 06:47:12

I think that class is not a supported attribute. You could though do this:

<txp:evaluate test="newer,older">
	<nav class="sb74-pagination" aria-label="<txp:text item="page_nav" />">
		<div  class="sb74-button">
			<txp:newer rel="prev">
				<txp:text item="newer" />
			</txp:newer>
		</div>
		<div  class="sb74-button">
			<txp:older rel="next" class="sb74-button">
				<txp:text item="older" />
			</txp:older>
		</div>
	</nav>
</txp:evaluate>

Bloke · 2021-02-22 07:53:02

class and html_id are global, so it should work. Unless the tag itself is overriding this behaviour for some reason.

etc · 2021-02-22 09:13:07

colak wrote #329012:

I think that class is not a supported attribute.

Bloke wrote #329013:

class and html_id are global, so it should work.

It would, if you supplied wraptag attribute. For example, with ...<txp:newer rel="prev" wraptag="div" class="sb74-button">... you’d get what Yiannis suggests.

Without wraptag, the global class and html_id have no idea where to apply themselves.

sambooth74 · 2021-02-22 09:22:51

etc wrote #329016:

It would, if you supplied wraptag attribute. For example, with ...<txp:newer rel="prev" wraptag="div" class="sb74-button">... you’d get what Yiannis suggests.

Without wraptag, the global class and html_id have no idea where to apply themselves.

That explains it, thank you. However I’m now getting 2 A tags.

<a class="sb74-button">
    <a rel="next" href="https://sb74.net/preview/?pg=2">Older</a>
</a>

Is there any way of telling TextPattern to apply the class attribute to the same A element as the rel attribute?

etc · 2021-02-22 09:45:36

sambooth74 wrote #329018:

However I’m now getting 2 A tags.

With wraptag="a"?

Is there any way of telling TextPattern to apply the class attribute to the same A element as the rel attribute?

No, I’m afraid. Global wraptag is completely agnostic of what it is wrapping. You can try

<txp:evaluate test="evaluate">
	<nav class="sb74-pagination" aria-label="<txp:text item="page_nav" />">
		<txp:evaluate test="newer"><a rel="prev" class="sb74-button" href="<txp:newer />">
			<txp:text item="newer" />
		</a></txp:evaluate>
		<txp:evaluate test="older"><a rel="next" class="sb74-button" href="<txp:older />">
			<txp:text item="older" />
		</a></txp:evaluate>
	</nav>
</txp:evaluate>

If we have time before 4.8.5 release, I can try to add proper class and html_id to older/newer tags.

sambooth74 · 2021-02-22 10:04:07

etc wrote #329021:

With wraptag="a"?

No, I’m afraid. Global wraptag is completely agnostic of what it is wrapping. You can try

<txp:evaluate test="evaluate">...

If we have time before 4.8.5 release, I can try to add proper class and html_id to older/newer tags.

That solved my problem, many thanks. Hopefully after a few more months of using Textpattern, I will understand the software enough to fix some of these issues myself. I feel like I am still learning the basics, and me creating my own theme will be a good way to understand the Textpattern way of thinking.

Thanks again.

etc · 2021-02-22 10:04:58

Meanwhile you can try etc_attribute. Adding class="a" to its preference should make your original code work.

But then be careful to call global wraptag before class in attributes when both are needed.

etc · 2021-02-22 10:09:31

sambooth74 wrote #329024:

Hopefully after a few more months of using Textpattern, I will understand the software enough to fix some of these issues myself. I feel like I am still learning the basics, and me creating my own theme will be a good way to understand the Textpattern way of thinking.

You are welcome. Textpattern is a mix of legacy code with more recent additions. For bw-compatibility reasons, not everything is completely uniform yet.

Textpattern CMS

Textpattern CMS support forum

#1 2021-02-21 17:49:59