Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Extending Page Naming Convention


Go to End


2 Posts   915 Views

Avatar
spankmaster79

Community Member, 46 Posts

9 December 2010 at 6:16am

Hi,

this might be a simple question.

I want to know if all Pages that extend Page have to be named Page at the end, like HomePAGE, ContentPAGE or DistributionPAGE. Or can I name them Home, Content and Distribution.

I run into Bad class to singleton errors calling the admin with index.php/admin. Using .htaccess and only /admin works. I really don't get the difference and it's kind of confusing.

Thx
Spanky

Avatar
swaiba

Forum Moderator, 1899 Posts

9 December 2010 at 7:05am

Edited: 09/12/2010 7:06am

As far as I know you can name them whatever you like, but it is good practice to name things in a was that reminds you what the class is.

Regarding "admin" vs "index.php/admin" the index.php with silverstripe simulates having mod_rewrite - if you can actually have mod_rewrite (that is sounds like you have because it works without index.php) then you should delete it from your installation.