Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sync article and article_custom attributes or generate warnings #457

Closed
vanmelick opened this issue Jan 2, 2015 · 5 comments
Closed

sync article and article_custom attributes or generate warnings #457

vanmelick opened this issue Jan 2, 2015 · 5 comments

Comments

@vanmelick
Copy link
Contributor

See this topic
http://forum.textpattern.com/viewtopic.php?id=44115&p=1

The user has excerpted="y" as an attribute in the txp:article tag, which isn't valid, but doesn't generate a warning, thus causing confusion. There should be a warning about using an unknown attribute or txp:article should handle the attribute as txp:article_custom does.

@Bloke
Copy link
Member

Bloke commented Jan 3, 2015

Yes, this is always a source of annoyance since <txp:article> is just a specialised version of <txp:article_custom> and uses most of the same code. As you know, the upshot is that you can put any attributes you like that are valid for article_custom into a regular article tag, and they'll mostly be silently ignored.

This could probably be changed with some if $(is_custom) stuff to detect which attributes have been supplied and throw appropriate warnings, just never really investigated how best to untangle the two.

@vanmelick
Copy link
Contributor Author

See pull request.

Additionally, I wonder why TXP accepts 'y' as a valid value for that attribute, while TXP uses 0 or 1 for boolean attributes in all other places. Shouldn't that be corrected as well for consistency?

rwetzlmayr added a commit that referenced this issue Aug 10, 2015
@rwetzlmayr
Copy link
Contributor

Refs #511

@rwetzlmayr
Copy link
Contributor

Additionally, I wonder why TXP accepts 'y' as a valid value for that attribute, while TXP uses 0 or 1 for boolean attributes in all other places. Shouldn't that be corrected as well for consistency?

+1

@Bloke
Copy link
Member

Bloke commented Aug 15, 2015

Closed by 26db124

@Bloke Bloke closed this as completed Aug 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants