Share your MODx secrets!

Not so much a ’MODx Secret’ per-se, but ...

Once I log into the MODx back-end, I almost always copy the manager window across one or more browser tabs. One tab to manager resources, another for chunks, the other for snippets (for example).

I get work done so much faster this way. All manager instances read from the same initial login, so you aren’t juggling multiple sessions.

Three caveats: (1) refresh the resource browsers regularly, and (2) beware modifying the site config with multiple back-end tabs open, and (3) Watch your browser memory consumption - things could start getting sluggish.

- Mike

RE: Jarnokk -- solution to work side by side with modx and existing pages:

Another simple method to install modx on an existing site that already uses index.php in the root is to rename the former index.php (eg: index1.php), then set the root .htaccess file to: DirectoryIndex index1.php. That frees up index.php to be used by modx.

This allows clients to view new pages while you develop them in modx, but other viewers are unlikely to see them (unless they enter the full homepage url -- http://www.domain.com/index.php -- in their browser). I just warn clients that clicking on the modx home nav button will return them to their existing homepage, not the modx homepage. For that they can use their browser back button or else re-enter the homepage url.

When you’re ready to go live with your new modx pages, just remove this .htaccess setting.

BTW, you may receive an error when accessing modx manager while using this method. Just use the full url to the manager (http://www.mynewsite.com/manager/index.php) and the manager loads.

I was running almost 25 to 1 with SPAM comments in Jot - and I really don’t like Captchas. Many of the comments were coming from the same IP addresses. So I created a simple filter that lets me add these addresses to a ’blocked’ list.

There is only a relatively small hack to Jot. Adding a button to the jot.comment.tpl and a few lines of code at the beginning of the Jot snippet to instantiate a class and call the two functions. None of the Jot code was modified.

A description and the code is at http://www.timr.ca/RecentArticles/cms/spam-filter-for-jot.html

In Evolution, once you save a resource, you can’t undo any previous changes. This is due to a page refresh after each save (and lack of built-in versioning).

Until Revolution has a versioning package available, there is a way to undo multiple levels even through page saves. As long as you stay on one page editing the same resource or element, you can undo multiple levels of edits even though incremental saves. This is because the architects of Revolution designed resources and elements to be saved and updated without reloading the workspace.

All you have to do is give the editing area focus (by clicking on a textarea or RTE), and hit Ctrl-Z as many times to undo to the level you require, up to the point where you opened the resource for editing.

That’s an awesome tip cyclissmo and one I’ve used but never thought to talk about it. Thanks!

i use the ctrl-z trick all the time when tweaking .css files via the revolution manager. love it.

This is probably not a secret to most but it opened up new doors for me—and big thanks to sottwell (per usual, to the rescue) for the help.

I had a situation where I needed users to be able to check which colors applied to a product—a checkbox TV right? Duh. Well, now what? At first I tried multiple @CHUNK bindings but that doesn’t work so here’s what does work (see screenshot and note the default values as well for common color applications).

BlakeWilliams, Thanks for the tip. Definitely will use this.

I don’t post often but I would like to share some tips on firing up a new MODx install. It can be a bear for those new to the install process.

Several tips regarding project startup w/ MODx - Working in clean directories.

1st RE: Jarnokk -- solution to work side by side with MODx and existing pages:
(cool solution Puffin) Here is another:

When redesigning a static website for a customer.
Keep the existing website Live but work MODx in a clean root directory.

Create a new directory in the root.
For example if you are building for a lawn service company Make a directory called lawn-services. Move the entire website into that directory clearing the root of all files and folders except lawn-services.

Create a .htacces file as mentioned above only place a 301 redirect in the .htaccess file.

Ie... -----


----
You do not need an index.html in the directory. When anyone types in either lawnservicecompany.com or www.lawnservicecompany.com it will forward to the full www.lawnservicecompany.com/lawn-services/index.htm,html,php the additional rewrite rule kills buggy results when forwarding to lawnservicecompany.com/lawn-services/index.htm,html,php without the www.
When you manually type in lawnservicecompany.com/index.php - The MODx version will load your site in root directory.

Now your root directory is empty of non MODx created files and directories. When the project is complete. Delete the 301 redirect. Delete the lawn-services folder. No picking through a mess of directories and files. Done deal. Your live.

Next TIP the MODx install – cPanel style-

From nothing to MODx manager panel login – 10 minutes.
A process to facilitate fast and successful installs.

Open 4 browser tabs –

TAB - cPanel - MySQL Databases
TAB - cPanel – File Manager
TAB - Browse to your future install directory /setup – 404 not-found
TAB - Browse to http://modxcms.com/download/

--- 2 minutes

TAB - http://modxcms.com/download/

Download your file of choice – While downloading open and prep your FTP utility of choice.

--- 2 Minutes

FTP utility

Upload the zip file to your directory of choice.
(Note: Uploading unpacked zip files can take 10-15 minutes depending on connection. Uploading the zip file. 2 minutes.)

During Zip file upload.

TAB - cPanel - MySQL Databases

Enter a database name in input field. Hit create database button. - go back.

Create username and password – hit create user button. Then go back. (You will need to remember this password for MODx install)

Add user to database – (select match from drop down) - add button – select all privileges – go back.

Database setup is complete in 2 minutes.
Your FTP of zip file is complete.

--- 2 Minutes

TAB - cPanel – File Manager

Check the checkbox beside MODx .zip file – look to top right – select extract. Accept extraction - Bam – 2 seconds all files and directories are installed. – Hit refresh for good measure.

TAB - install directory / setup – Hit Refresh
Choose language – select

Welcome to MODx – Next

New Installation – (It is best to leave file and folder permissions as is unless you have specific needs.) – Next

Connection Information (okay – the first time I installed MODx getting the right combination of database name – username threw me for a loop. So for those new to MODx here is a great trick)

Bounce back to TAB - cPanel - MySQL Databases

Highlight the entire username with curser (careful not to grab the x) copy – jump back to MODx setup and paste into Database login name:
same for Database name: and the password is the user password you created a minute ago.
Personalize the database table prefix (keep trailing underscore_)

Test database server connection and view collations.
Connecting to mysql server: Success!

Leave the default Connection character set and Collation as is.

Create or test selection of your database.
Checking database:Success!

Create default super admin – email address is key to resetting lost password.

Next –
Install –
Toggle success messages.
Next-
Check this to DELETE the setup directory from the file system. YES. DO CHECK.
Login –

---4 Minutes

2-2-2-4 10 minute install.

Sweet. Revolution rocks.

Regards,
William

this is the one i usually use ... my friend introduced it to me

http://wiki.modxcms.com/index.php/Customizing_the_Manager_Homepage