How to write modules?

MODX Staff
10,725 Posts

opengeek Reply #11, 20 years ago

You’ll need to call the manager/processors/cache_sync.processor.php to refresh the site configuration file with the modified system settings.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

155 Posts

Boby Reply #12, 20 years ago

Quote from: OpenGeek at Sep 02, 2006, 07:13 PM

You’ll need to call the manager/processors/cache_sync.processor.php to refresh the site configuration file with the modified system settings.

So, is this ok or do I have to call it in an other way?

<?php
   require_once $modx->config['base_path'].'manager/processors/cache_sync.class.processor.php';
   $cache_sync = new synccache;
   $cache_sync->setCachepath($modx->config['base_path'].'assets/cache/');
   $cache_sync->emptyCache();
?>

Ooohh, and do I have to call this on module start or right after the modx_system_settings table was updated?

Thank you!
Boby

...my Photo Gallery on Flickr...

MODX Staff
1,535 Posts

Garry Nutting Reply #13, 20 years ago

Hi Boby, the code looks to be fine. You will need to call the code after you have updated the table values.

Garry Nutting
Senior Developer
MODX, LLC

Email: [email protected]
Twitter: @garryn
Web: modx.com

☆ A M B ☆
24,524 Posts

sottwell Reply #14, 20 years ago

I’m documenting the process of developing an AJAX-enhanced database manager module on my site; log in as the guest Manager user and check it out.

http://www.sottwell.com/database-module.html

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

65 Posts

JoeP Reply #15, 19 years, 11 months ago

The link seems to be broken.

65 Posts

JoeP Reply #16, 19 years, 11 months ago

Quote from: xwisdom at Aug 08, 2005, 08:16 PM

Yes most things can be converted into modules but somethings are better integrated.

Is there any documentation on how to integrate an externa application? I have several apps that each have their own user admin pages e.g. an even calendar, a photo gallery, etc. From what I read, I could just include these as modules "but somethings are better integrated".

It would be intersting / educational / helpful to have a description of the process that was used for integration of SMF and/or other similar app. One of the primary concerns is to do the integration in such a way that upgrades to the integrated app can be supported without having to completely hack the app.

Thanks,
joe

MODX Staff
10,725 Posts

opengeek Reply #17, 19 years, 11 months ago

Quote from: JoeP at Oct 14, 2006, 09:42 AM

Is there any documentation on how to integrate an externa application? I have several apps that each have their own user admin pages e.g. an even calendar, a photo gallery, etc. From what I read, I could just include these as modules "but somethings are better integrated".

It would be intersting / educational / helpful to have a description of the process that was used for integration of SMF and/or other similar app. One of the primary concerns is to do the integration in such a way that upgrades to the integrated app can be supported without having to completely hack the app.

@JoeP: currently there is no documentation on this process, for a couple of reasons...

First, we are still developing the application, and current plans will see the current core code-base completely replaced before the 1.0 release. And a key factor in this rewrite is the ability to extend or override core behavior without changing the core code at all, along with other architectural issues that will make the job of integrating a wider variety of 3rd party applications with MODx much easier.

Second, even we can’t all agree on the best way to integrate things with MODx. There are still so many unexplored techniques and untried features in MODx, it’s difficult to decide if what you did is the best way or not, so documenting it often seems fruitless. I often do something one way, and end up completely changing the original approach after discovering a new feature or technique, or just thinking about something I didn’t consider the first time around.

Hopefully, the new MODx wiki, which is just getting started and will likely be officially announced this weekend, will be a great place for users to share best practice experiences with these kinds of projects.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

65 Posts

JoeP Reply #18, 19 years, 11 months ago

Quote from: OpenGeek at Oct 14, 2006, 12:47 PM

<snip>
First, we are still developing the application, and current plans will see the current core code-base completely replaced before the 1.0 release. </snip>

I kinda figured (hoped) that since 0.9.5 beta3 is currently available that it was going to be pretty close to the 1.0 release. How far off do you think (guess) 1.0 is going to be? I’ve read elsewhere that an upgrade path has been a top priority... still true?
Thanks much!
joe

MODX Staff
10,725 Posts

opengeek Reply #19, 19 years, 11 months ago

Quote from: JoeP at Oct 15, 2006, 08:47 AM

I kinda figured (hoped) that since 0.9.5 beta3 is currently available that it was going to be pretty close to the 1.0 release. How far off do you think (guess) 1.0 is going to be? I’ve read elsewhere that an upgrade path has been a top priority... still true?
Thanks much!
joe

I definitely don’t want to guess. I have my goals, but sharing those is dangerous around here, because we all know that goals have to be adjusted for unknowns, and we’ve encountered plenty of those along the way already. The upgrade path is of course a top priority, though that does little to help speed delivery. Truth is, there is a lot of development going on in the team, and coordinating it all, especially when trying to replace the entire existing code-base, is no easy challenge, but one I find exciting and rewarding.

Note that I’m also not one for arbitrarily skipping versions. We’re about to unveil major release 0, version 9, small version 5, and we have at least one, possible more, stepping stone (i.e. small version) releases left before 1.0 comes to fruition. The most important reason in my mind that we are choosing to keep these releases on the same major release number (0) is that we want to shed our status as an Etomite fork with 1.0.

Please realize that just because it is pre-1.0, this does not in any way mean that MODx is not stable or production ready. I’ve used just about every major release of MODx (as well as many interim or custom releases) for over a year and a half on production sites.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

65 Posts

JoeP Reply #20, 19 years, 11 months ago

Quote from: OpenGeek at Oct 15, 2006, 04:45 PM

Please realize that just because it is pre-1.0, this does not in any way mean that MODx is not stable or production ready. I’ve used just about every major release of MODx (as well as many interim or custom releases) for over a year and a half on production sites.

No worries!
I’ve been playing with 0.95 beta 3 for less than 8 hours and am already in love rolleyes

.
I’m planning on (started already) moving everything to MODx.
Thanks for the quick and thoughtfull response(s)!
A new true believer grin

joe