Plugin order

Is someone actively solving a module order quest? As stated previously in some old and short thread, the target is that we would be able to set the order of triggering modules on some event.

If not, I would probably have a look at some neat and robust solution ideas.

I think this would be usefull, really big move up.

I am working on a solution that will allow chains of content elements to be processed in a certain order for the 1.0 rewrite. I have not had a look at doing it in the current releases, but the new solution allows all content elements to define an order/priority, and the core, as well as other elements, can then use this priority information to process the elements in a certain order. In addition, elements can define if they should allow a chain of elements to continue processing, or if it should stop processing additional elements under specific conditions (i.e. an element in the middle of the chain indicates it should stop by setting a flag).

OK, I won’t disturb you and look at the caching instead.

Quote from: tillda at Jul 09, 2006, 04:21 PM

OK, I won’t disturb you and look at the caching instead.

Also, in regards to caching static html files, I think it might be worth looking to extend/integrate the capabilities of the site export in conjunction with the cache synchronization mechanism. What I’m envisioning is the ability to have super-cacheable documents, in other words, a specific document could be exported as static html when saved, placed in the proper location based on friendly URL settings, and then MODx could be bypassed completely on those requests with no other changes.

Thoughts?

Quote from: OpenGeek at Jul 09, 2006, 05:58 PM

Also, in regards to caching static html files, I think it might be worth looking to extend/integrate the capabilities of the site export in conjunction with the cache synchronization mechanism. What I’m envisioning is the ability to have super-cacheable documents, in other words, a specific document could be exported as static html when saved, placed in the proper location based on friendly URL settings, and then MODx could be bypassed completely on those requests with no other changes.

I’m not sure what you mean now, I think it’s *exactly* what i outlined here: http://modxcms.com/forums/index.php/topic,5684.msg40179.html#msg40179

The only problem is, that it’s not so simple - for example my site (www.dotprofit.cz) - has short news on the right side in all templates. So, if I add a news, all cached data should be deleted in not so long time. And this must be carefully ballanced to provide computer-time savings as long as reasonable refresh interval.