MODX Staff
It’s not any easier or harder with MODx at this point. And don’t use RTE’s to enter markup and javascript if you want control over it. RTE’s are for end-users to be able to update small, isolated sections of content that can’t mess up the layout of the site.
I want to start using AJAX technology and found that it is easy with simple PHP pages, but not that easy with MODx. Questions:
- I cannot write JavaScript code directly in a page (i.e. using the content editor), even if editing HTML: FCKeditor likes to mess the JavaScript code. The best way I found is to create a chunk and write the snippet there.
I’m not exactly following. You need to provide the ajax handler. The index-ajax.php just helps you get access to the MODx database configuration details if you need db access in your handler.
- As for PHP side, I can of course write a PHP page that process async request and send the XML/JSON/whatever reply, but I have to upload that file and this is odd. I use a snippet and a blank template (with only the [*content*]). In this way I can put the code in the snippet and the snippet in a page. It’s more MODxish. Is there any better way to do this? I see a index-ajax.php in the root directory, but I cannot have anything better than a "Cannot load requested ajax handler" message
Quote from: madmage at Dec 19, 2006, 04:07 PMI’m not exactly following. You need to provide the ajax handler. The index-ajax.php just helps you get access to the MODx database configuration details if you need db access in your handler.
- As for PHP side, I can of course write a PHP page that process async request and send the XML/JSON/whatever reply, but I have to upload that file and this is odd. I use a snippet and a blank template (with only the [*content*]). In this way I can put the code in the snippet and the snippet in a page. It’s more MODxish. Is there any better way to do this? I see a index-ajax.php in the root directory, but I cannot have anything better than a "Cannot load requested ajax handler" message
MODX Staff
That’s right. Having virtual MODx documents as AJAX handlers in this version of MODx is, well, not the best approach IMO, because you are bootstrapping a lot of unnecessary code to that end. The purpose of providing index-ajax.php was as a temporary solution for accessing the MODx database in your own AJAX code (separate PHP script). In the next release, you will be able to do what you are describing as the new MODx core coming in 0.9.7 only loads what it needs to. In addition, I plan to have a basic class you can extend to handle typical AJAX requests as "documents" managed by MODx, along with some other surprises.
When you say "AJAX handler" you mean a PHP page, right?
but that page cannot be in the site_content table, it has to be a separated file, right?
Quote from: madmage at Dec 23, 2006, 04:50 PMThat’s right. Having virtual MODx documents as AJAX handlers in this version of MODx is, well, not the best approach IMO, because you are bootstrapping a lot of unnecessary code to that end. The purpose of providing index-ajax.php was as a temporary solution for accessing the MODx database in your own AJAX code (separate PHP script). In the next release, you will be able to do what you are describing as the new MODx core coming in 0.9.7 only loads what it needs to. In addition, I plan to have a basic class you can extend to handle typical AJAX requests as "documents" managed by MODx, along with some other surprises.
When you say "AJAX handler" you mean a PHP page, right?
but that page cannot be in the site_content table, it has to be a separated file, right?