-
☆ A M B ☆
- 1,780 Posts
I saw this (or something similar - with the smarty error) recently in a move, a reinstall fixed it up though. Do like you're updating MODX, get a fresh copy of the zip file unpack on the server, merge the files with the existing installation and re-run setup.
Clear the cache manually first though.
Well now that's weird...
I already did exactly as you suggested - twice in fact - before I'd posted the above message... the same errors appearing both times. It got to 1am and that's when I left it in case I started making stupid mistakes.
Now this morning it's fine.
If you don't mind me asking, which hosting company did you use when you received the smarty error? This was all happening on nethosted. I'd love to hear what anyone in the modx dev team has to say about it.
-
☆ A M B ☆
- 1,780 Posts
IIRC, it was on a Hostmonster server. Either that or Hostgator. Hostgator provides an excellent server for MODX, and Hostmonster seems to be as well (so far).
It's just shy of 1am here actually :~}
Chances are, it was a corrupted smarty file, and for some reason your cache didn't get cleared properly or the browser cache remained, so it was pulling the old error. I've seen MODX fix itself overnight before as well, I know now it was most likely the browser cache.
I've got a couple of servers with nethosted and never had any problems with them, in fact I've found they give the best support that I have ever come across.
Even the best of us can run into problems when moving a revo site, I had one last night and ended up dropping the database, doing a fresh install and then putting my original database back in to solve the problems.
Slight misinformation before - I just saw another message from the nethosted support saying he'd had to change some file-paths in one of the config files, which has now solved the issue.
Paulp - you're absolutely right - I've never had cause to complain about nethosted's support - they're an excellent team.
I was wondering if someone knew of a wiki/webpage/rtfm about exactly how to configure the paths in the config files... seems like a much overlooked resource.
I sort of followed that set of instructions anyway - although one or two of the videos I found, also going through the process, proved much more helpful. What I meant was more of an instruction as to exactly what to alter the file-paths to on a new server, rather than an overall process.
TBH, I don't like the way that link you cited is written - I understand that it'll be different in the different environments, but to me the article's just not quite clear enough.
Anyway, I appreciate all the replies and pointers, as usual.
-
☆ A M B ☆
- 1,780 Posts
Exactly what to alter the paths to depends on where MODX is installed. Although some clearer examples could be shown. An example of a root install, and a subfolder install comes to mind as what's missing.
What was helpful for you from the videos, that isn't in the Documentation?
I think I "get" the specifics required for a subfolder installation - on WAMP at least.
I think the problem arose when I searched through the nethosted FAQs to see what paths I should enter when I migrated. I experienced a few problems, which their support team semi-ironed out (after which I posted on here), but not entirely. It then transpired that the amendments they'd made somehow weren't quite right, and they'd subsequently fixed the issue completely a couple of hours later.
My point is there was no clear indication, anywhere that I could find, that categorically stated what the new file-paths ought to be. I can't imagine I'm the only person for this to be something of a headache.
Regarding the videos, I'm not sure they necessarily covered anything extra, but a visual guide tells a much better story than the rtfm does. Perhaps it's mere preference, or a lack of experience. But it wouldn't be the first time that I've hesitated and had to re-read pieces of the modx documentation, before I can even begin to feel confident enough to work with it.
MODX Staff