New to Modx - Small issue

Hello.

My name is Mark dunbavan. I have just installed Modx for the first time and everything went smoothly
with install and setup etc but I ran into a problem when I went to login. This is the message that appeared
when I logged in and pressed enter;

’Fatal error: require_once() [function.require]: Failed opening required ’/home/fhlinux209/m/markdunbavan.co.uk/user/htdocs/core/model/modx/processors/security/login.php’ (include_path=’.:/usr/share/pear-php5’) in /home/fhlinux209/m/markdunbavan.co.uk/user/htdocs/manager/controllers/default/security/login.php on line 59 ’

Can anyone guess what might be causing this error to happen?

The version of Modx was the current version only downloaded today.
The download was basic package.
The server is Linux
php version 5.5

Any help would be great thanks,

Mark

Hi Mark - that’s not a good start!!

I don’t know a lot about these kind of errors, but it seems you’re not the first this has happened to. Maybe the paths have been configured incorrectly and it’s not finding those crucial login files.

Something that worked previously was to:

• Browse to your core/cache/ folder and delete everything except index.php
• Clear your browser cache and delete cookies
• Run setup again

Give that a go and report back...

Luke

Huh… PHP 5.5 is pretty new and not stable I think. Do you have PEAR lib included?
Are both files (encountering troubles) having correct permissions and are available on server?

Hi Lucas.

Its all gone wrong now and it now comes up with a 503 error. Site temp unavailable.

I am unsure as to whether there is PEAR Lib included on the server.

Do you think its just worth me re-installing everything again and systematically going through all the files
that include the core config paths and making them direct to my server?

Thanks

Mark

Did you run setup again?

I am going to do that now and see what happens.

Just to make sure, when I go into the core config php files I need to make sure the path directs to my root directory?

must have been a technical glitch in the first install. It works like a charm now.

Thanks for your support guys its much appreciated.

Regards

Mark

No problem Mark... now you’re in, you’re gonna love MODx

I know I have heard lots about it.

Just a couple of quick questions, Do you know how easy it is to integrate html5 into the build? Also, when developing a normal site within the template section
from my own markup does the cms automatically put prefixes around tags to represent the cms itself, I guess what I am simply asking is how does it manifest itself within my
own markup?

Thanks

Mark

Your template can be anything you want. MODx doesn’t care; it just spits out what you put into the template + the output of whatever MODx tags you’ve used. The whole point of the parser is to parse the requested page’s template and process any MODx tags in that template. If a "blank" template is specified, it uses the resource content instead.

If you copy/paste a view source from any web page of any type into a template, that’s exactly what you’ll get back if you request a page using that template.

I only work with HTML 5 now.