modx

I have a website using MODx Revolution (2.2.10-pl, advanced install), let's call it www.example.com , which I want to be accessible with both http and https. to achieve this, I tweaked the site_url context setting to be [[++url_scheme]]www.example.com/ . Links created using [[~id]] seem to be alright, however, sometimes, the generated links are really weird. My interpretation is that the code to create links programmatically doesn't work with my settings, but I don't know why, or how else I would go about enabling both http and https. Question first, examples below: How should I set the site

I have a site which has been built in modx and when its hit with load uses up all cpu processing power and top is showing a lot of defunct php zombie processes consuming this. Here's the system specs... PHP 5.2.14 php running as suPHP Mysql 5.1.51 Apache 2.0.63 modx 1.0.4 For testing im using ApacheBench and simulating 500 connections with 100 concurrent connections I've tested this out 2 ways now... Turning off .htaccess and stress testing a simple php page that just echoes 'Hello world'. In top this shows php going defunct and turning into a zombie but they go away pretty quickly Calling a

Has anyone come up with a way to speed up the backend in modx? I was thinking that creating a set of pages in modx with admin privileges to modify the site content, so that it looks customized, works in IE and is not slow. Any thoughts on this? What version of Revolution are you using? In the latest release (2.07) a lot of work has been done on the manager and it has been claimed pages will load 50% faster than in previous releases. works in IE and is not slow turn off firebug and your problem is solved. Chrome works best for me...and modx 2.0.7 works faster. edit: Some people said that it

I developed a site for a client before a domain name was chosen. As a result, the URLs for the site pages look like: http://host.mynost.net/~tempname/index.php?id=8 A domain name has now been purchased but if I click on any Wayfinder links it still uses the old path as above instead of, say: http://domainname.com/index.php?id=8 I assume this is configured in the config.inc.php file, but I am unsure of what to change. Can anyone point me in the right direction? Thanks! You need to change $modx_base_url= '/' in /core/config/config.inc.php and if that is not enough - manually clean /core/cache/

I have an MODX site running on the shared server in the root folder (i.e. public/www/). I also have an MODX testing site running in the subfolder (public/www/modxtest). I want to move this testing site into the root in a way that the modx site in root folder is not affectetd until the end of migration. I haven't touched MODX before and do not know the migration procedure. One way of doing that may be using htaccess file and redirect the request to the root MODX site to the subfolder MODX site as in https://my.bluehost.com/cgi/help/347 This method might get confusing for other person as they