Is ModX CMS better than Joomla ?

Letti,
Ah, with that "#", yeah, you must have JQuery or something if those links actually work. You’re right, with that link, I’m pretty sure no way my solution (or any Wayfinder solution) will work, because it depends on an actual link. You’d have to write JQuery code to produce the SSL links. I may be full of bollocks, but that’s what happens when there’s no link to look at.

I took your acc-folder code and stuck Ryan’s idea in there so you not only have a link, but have the secure stuff. Why not give it a try with JQuery shut off, and then you can at least see if MODx is doing its thing:



Cheers, Dave

Hi Dave,

and what do you think of our code for the .htaccess-file? Do you have any idea what we have to change making the sites completely ssl-encrypted? At the moment with this code the browsers still complain of not fully ssl-encrypted site-content...

If you want to force the ENTIRE site to be HTTPS only, you can use an .htaccess rule like this:



Replace the IP address with your dedicated IP address.

Hi Everett,

to encrypt the whole page ist not really bad but there is one disadvantage. If all your paths of the website-elements (pictures and so on) are not relative you will get errors in your browser reporting your connection is not fully protected.

Therefore we were going to encrypt only single pages where we can ensure that every element is loaded correctly in a ssl-way...

Never say it’s not possible to do something on MODx


Wayfinder still uses a default rowTpl if you don’t supply one. How else would it output something?

This is the default that is hardcoded in the code:


To modify this to make it all SSL links you’ll get:



To modify that to make SSL links based on wether or not a TV called forceSSL has a value of 1:



Untested. But imo should do the trick.

Put that code in a chunk, and reference it to the &rowTpl parameter in your wayfinder call.

You can set up the TV as a checkbox. Set input option values to "1==Yes, make SSL links". If you want to turn it on by default set the default option values to "1".


Anything’s possible in MODx.

(So does that make it better then Joomla for us developers? I’d say so... )

Quote from: Letti at Dec 21, 2010, 04:44 AM

Hi Everett,

to encrypt the whole page ist not really bad but there is one disadvantage. If all your paths of the website-elements (pictures and so on) are not relative you will get errors in your browser reporting your connection is not fully protected.

Therefore we were going to encrypt only single pages where we can ensure that every element is loaded correctly in a ssl-way...

Letti,
To answer your question, I don’t know enough mod_rewrite programming to diagnose your original .htaccess file. I probably would have tried something like Everett’s method. If you have those very specific needs, I think you’ll need to find a mod_rewrite expert, possibly a server admin or the like. And if your host is excellent, their tech support may have some ideas (not Godaddy or the like).

If the problem is absolute paths, I should think that it’s not too hard to try relative paths in your templates and such. MODx is very good at relative paths (by contrast, Wordpress is all about absolute paths). But again, I’m out of my element there.

Good luck, D

I started out with Joomla and even bought a book, then I installed MODx... What’s different
with MODx, is that you decide how much you want to integrate the functionality of it into your
design and code. Not the other way around. This is the main reason why its easy to get nice
SEO with MODx. But to tell the truth, you will need to be a geek and not be afraid of learning
to adjust PHP and "get your hands dirty". But if you choose the red pill there is no turning back!

Letti-

It’s not the relative paths that cause errors: you will get warnings if you mix both http and https components on a page because your page then contains secure and non-secure parts. Using relative paths can help side-step this problem because a relative path will assume the protocol used by accessing the original page -- e.g. if you access the original page via https, then the src="assets/images/img.jpg" will also be accessed via https.

In general, I find it easier to force an entire site to be https -- then you’re less likely to run into the secure/non-secure problems, or the problems of having a "secure" page potentially accessible via http.

i’m getting seriously seo-spam paranoid. don’t know why, but it bothers me a lot. that’s all.

The guy starting this thread (and other threats) is spamming. There is no sign of Modx on his page. He has links to his commercial pages all over, so out with him i dd say.