21307 Posts in 5737 Topics by 2603 members
| Go to End | Next > | |
| Author | Topic: | 915 Views |
-
Broken CMS

11 August 2010 at 3:51am
Hi Chaps,
Im almost to the point of unvailing the new silverstripe intranet site to my company.
I have been tweaking a few things and have managed to kind of break it!I have built an article system as per the docs on the help system.
This worked fine. Got a homepage created that displays the latest 5 entries and then tickered it using jQuery in a BBC stylee.I then realised that all the users would have to enter in their usernames when they create news. I have the bright idea of having it auto populate this field based on who is logged in.
So i added this to the article page :public function populateDefaults() {
parent::populateDefaults();
$memberName = Member::currentUser() ? Member::currentUser()->getName() : null;
$this->setField('Author', $memberName);
}As per another forum post i found.
Works great!My only issue is now that pages that were created before that mod are uneditable from the CMS.
I can remove them from the published site but whenever i try to remove them completely from the CMS i get a red 'server error'.Im guessing its because those posts no longer relate to the tables in the database.
My question is how to get rid of these from the site?
Can anyone point me in the right direction please?
Many Thanks
Craig -
Re: Broken CMS

11 August 2010 at 10:19pm
The server error message is not very useful. You can see the full error message in your browsers error console (firefox at least) or in your php error log.
-
Re: Broken CMS

17 August 2010 at 1:50am
Hi Wil,
sorry mate, been crazy busy.
Ive looked at the page using firebug and get this (screenshot attached)
to be fair it means absolutely nothing to me.
Have you got any ideas?
Anything more i can provide just let me know
Thanks alot!
Craig -
Re: Broken CMS

17 August 2010 at 10:10pm
I can see the words
500 Internal Server error which means the site is probably running in live mode so you won't see the actual error message outputted to the console. Check your error logs or turn on devmode to get the actual error message.
-
Re: Broken CMS

18 August 2010 at 9:09am
Tried checking the steps that error page lists to check. PROTIP If its hard to read in the console like that. You can right click, copy error and paste in a new text doc and it should be formatted a bit better.
| 915 Views | ||
| Go to Top | Next > |



