Blank page with www in URL

Hi, I tried without cache. Disabled from all pages’ settings and in the general settings set default to non-cacheable. Didn’t help. Any other suggestions?

Try making the cache files 666 and the cache folder 777

Quote from: rthrash at Nov 28, 2007, 01:47 PM

Try making the cache files 666 and the cache folder 777

There are no cache files now since I disabled the cache. And the problem still persists. So it can’t be the cause.

Are there any other places to configure access rights to the pages besides these:
1) Access permissions in the page settings
2) "Published?" in the page settings

Since this does seem like a rights issue, but the page overview says "Status: Published" and "Web access: public".

Try XAMPP

Quote from: rthrash at Nov 29, 2007, 08:36 AM

Try XAMPP

Sorry, I seem to be missing the point. I am sure MODx would work just fine if I install it locally, but how will that help me to get the website I’m working on to work?

It would allow you to confirm whether or not you have a PHP/Apache/MySQL/DNS/permissions configuration issue, and give you proof in order to work with your server admin to sort it out. Working without/with "www." in front of the url and not the other way around almost 100% of the time in the past points squarely at a server configuration problem.

There’s simply not enough information supplied to be able to determine any other cause. You might also want to see the "help us help you" link in my signature for typical info required in order to figure out problems.

Yes, at first I thought it was about the www, but then as I said, I noticed that I can not see the page even without www if I’m not logged in to the manager. And when I select preview from the manager, the page displays fine.

So, to me it seems like the problem involves MODx, since I can access normal files and html pages just fine with or without the www. Maybe just on this server, but I’m hoping someone could help me find out why so we can fix it with the server admin. It’s very hard to fix if we don’t know what is causing this.

Alright, here’s some info if this helps.

PHP Version 4.3.11
System Linux 2.6.19.2
Server API Apache
Apache/1.3.31
MySQL version 4.1.20-max-log
No DB tables above 1mb
MODx version 0.9.6.1, no modifications

At the moment I’m running the installer again, this time intalling the sample web site... to see if that helps.

UPDATE:
When I installed the sample website, it’s working fine now. Is there something important unconfigured in the empty installation, that has been pre-configured in the sample website..?

UPDATE2:
I was sure I found the problem since the sample website worked. So I installed the blank one again, and this time created an error page and an unauthorized access page, and changed their IDs into the fields in the configuration. But it didn’t help - after the cache was emptied there’s the blank page again... so clearly this is an issue with the blank installation, something’s missing that’s preconfigured into the sample website. If anyone knows what the missing pieces are, now would be a good time to say it.
I’m going to just make the website based on the sample website if no one is able to help on this during the weekend. But that doesn’t solve the problem in MODx blank installation (or at least documentation).

If there’s something wrong with the "blank" installation that’d be great to know indeed!

Why are you spending so much time with the successful install page? Which, if I had my way, wouldn’t exist at all; you’d get no pages in the default installation. A nice clean, blank slate. The whole point of MODx is to bring your content and design and requirements to the box, put them in, and tweak it to get out exactly what you want. I’d spend my time starting with the sample site (which got a lot more attention than the single-page install successful), learning from it, or start with your own designs or an open source template maybe, converting it to MODx based on studying the sample site. Just some ideas.

Anyway, there is likely some simple explanation for the www url not working in the source of that page, maybe related to some unnecessarily prefixed path in the content that is being cached, referring to whatever URL was first accessed and confusing it when accessing it from the other.

Quote from: OpenGeek at Nov 30, 2007, 10:09 AM

Why are you spending so much time with the successful install page? Which, if I had my way, wouldn’t exist at all; you’d get no pages in the default installation. A nice clean, blank slate. The whole point of MODx is to bring your content and design and requirements to the box, put them in, and tweak it to get out exactly what you want. I’d spend my time starting with the sample site (which got a lot more attention than the single-page install successful), learning from it, or start with your own designs or an open source template maybe, converting it to MODx based on studying the sample site. Just some ideas.

Anyway, there is likely some simple explanation for the www url not working in the source of that page, maybe related to some unnecessarily prefixed path in the content that is being cached, referring to whatever URL was first accessed and confusing it when accessing it from the other.

Umm... okay...