MODX Revolution News System

You can keep the URIs consistent even when using custom tables. Just needs a plugin to find the right blog/news post from your table, and display that from a resource (yes - you’ll need one to view the table content).

I’d argue that are a resource is anything that lives at the end of it’s own URI

That is an interesting statement. While true - it doesn’t take into account the resource aggregation often (if not always) used to display them in a list/grid, etc. Stuff like that can really take a performance hit imo as it also fetches unneccessary (meta) data. It’s just that this happens at the multiple thousands of resources when used wisely. The average website with some blog items wont have that issue very fast.



The fun part of MODX is that you can do it either way for whatever suits you and your client best.

How about making a rule in Form Customization module that all the news in the News container are hidden in the tree and when you click News in the tree you get redirected to the News CMP?

Does i make sense?

@cipa: that indeed would be a fast, easy and alternative way to do it (was thinking about that lately)

That would make management easier. Any idea how to accomplish that?

@Mark: besides launching the CMP from the three, i got some ideas on how it can be done. That almost the same stuff i did for "Asides", except we are dealing about modResouces instead of modChunks

Hi Romain;
Seems you forgot the Description in the Extra page for your Asides add-on.

« Asides is a MODX Extra allowing you to easily manage "asides" on a website, using chunks. »

Ok, probably not the best description ever… it’s an extra allowing you/your website’s editors to manage the « sections » in your sidebar (column, aside, whatever you call it).
But that’s offtopic. Send me a PM if you need more infos (or just give it a try ^^)

Quote from: Romain at Jun 05, 2011, 04:03 PM

« Asides is a MODX Extra allowing you to easily manage "asides" on a website, using chunks. »

Ok, probably not the best description ever… it’s an extra allowing you/your website’s editors to manage the « sections » in your sidebar (column, aside, whatever you call it).
But that’s offtopic. Send me a PM if you need more infos (or just give it a try ^^)

Is there an Asides sub forum on this board? I can’t seem to find it. I’ve input the category ID of the asides category and dropped a chunk in to that category.

I’ve granted access to the correct template for the asides TV.

I’ve put this in the template: [[showAside? &chunks=`[[*aside]]`]].

When I edit a page using that template I can see the Asides TV in the Template Variables tab and it lists the chunks I’ve put in the Asides category. It lists the name and if they are active or not by checkbox. How do you edit the contents? Or is it simply just to enable/disable the content?

Quote from: rx2 at Jun 08, 2011, 02:57 PM

Or is it simply just to enable/disable the content?

On the resource edition "mode" you can only enable/disable which aside you want to display. If you want to edit you’ll have to go through components » Asides, albeit the edition is kinda raw for now. You can either directly edit your chunk (with codemirror if you want to) within the element tab.

I’ve opened a thread in the extras forum

I still don’t see a reason to make a 3PC and think it’s a waste of effort. It could be better spend to remove limits from MODX, which force you to think about creating a 3PC.

There are 2 obstacles, which make managing a large number of resources not effective in MODX (well, actually managing a few dozens of them is hard):

• The resource tree, which is great for structure but not for content. It’s great for sections but not for publications (news, articles, products etc.). 30+ items make it unhandy in use. The solution would be to use a grid for displaying child resources (there was sth similar in Evo). This could be switchable on resource level, in FC and in resource class definition.


• The resource itself, which is document by default. There’s a discussion about what resource types should be and a ticket on it. In short, the modResource should be a skeleton for all resource types with minimal meta data, on which other types should be defined. Then you could define your news (or product, user, event etc.) resource type with all and only required fields.

All other functionality you mentioned is already there and ready to use.