[#10242] - Tag blog layout (RFC)
- Closed
- 5 Aug 2016
- Medium
- Build: staging
- # 10242
- Diff
- Bakual:TagBlogLayout
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
User tests: Successful: Unsuccessful:
This is a proof of concept PR based on a discussion in the Google Group (https://groups.google.com/d/msg/joomla-dev-cms/YVwuuNYHFUQ/hHs7_kaFAgAJ)
Summary of Changes
This PR would add a new layout to the tag view of com_tags which shows the items in a similar way the com_content blog layout does.
Since com_tags doesn't have all needed data for some extensions (like for com_contact) and since the various content types need different designs (eg a contact is different from an article) the layout uses content type specific JLayouts to render the items. If an extension doesn't provide a specific JLayout for its content type(s), a default fallback JLayout is used.
The JLayout for a contact will fetch the additional data using the components model. Imho, this isn't really nice from an architectural point of view but I don't see a simpler approach.
Testing Instructions
Create a new menu item for the new layout (currently untranslated, just take the ugly one) and tag content from various extensions (eg some contacts and articles) and see how they render.
Known issues
This PR is far from ready. Most menu parameters will not work and it is hardcoded to use two columns.
It is mainly meant to show how it could work and to open the discussion.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Labels |
Added:
?
|
||
| Category | ⇒ | Tags |
The default JLayout works with the data from the UCM tables. So yes. I did not create an own JLayout for the article to show the fallback mechanism. But we could do a JLayout for articles similar to the one I did for the contact. In that specific JLayout we could do whatever we want.
By the way, those JLayouts are fully overrideable in a template. Even if there is currently no article JLayout, you could still create one in your template and it would be picked up.
wilsonge
- | Labels |
Added:
?
|
||
| Title |
|
||||||
@bakual you created this as an RFC and there hasnt really been any Comments
Is this something you are going to continue with or abandon due to lack of interest?
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10242.
| Status | Pending | ⇒ | Information Required |
| Labels | |||
| Category | Tags | ⇒ | Front End Components Tags Layout |
It's not something I personally have any interest in getting into core. I did it to show how it could be done. But I agree there seems to be not much interest.
I'm going to close it. If the discussion comes up again, it can be revived anytime
| Status | Information Required | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-08-05 18:06:57 |
| Closed_By | ⇒ | Bakual | |
| Labels | |||
Thanks
I would love to see this implemented. Tags are great within Joomla however in its current state it is hard to find a real life purpose for them without a proper way to display their results when clicked. Tags by definition should allow users to filter content using the same view as where they are defined (eg. Category Blog). A quick search on the likes of StackOverflow and StackExchange shows plenty users looking for this very solution.
This pr does not do what you are asking. It creates a new menu type view
for tags.
Thank you @brianteeman .. my mistake. I found #10346 and the broader conversation been had on the subject.
Hi @bakual!
Am I wrong or this is pulling content data only from the
#_ucm_contenttable'score_bodyfield?That would mean you have access to the introtext only (then no fulltext...), right?