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're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

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

Order in which things happen in Silverstripe

Go to End



Community Member, 77 Posts

31 August 2012 at 8:30am

Edited: 01/09/2012 1:04am


I really like how Silverstripe core is kept so lean and mean whilst allowing developers to implement what is required. As a procedural ludite I have only just started to venture into developing object code and even I have now been able to implement a number of my own modules. In order to troubleshoot when things do not work, I think it is essential to know the order in which things happen. However I think my understanding of what happens is quite limited. I would like to find an explanation which refers to the different types of files used by Silverstripe when a module runs, and how these files and what they contain are brought into play and used. This would obviously make troubleshooting so much easier. On reading the documentation I have not been able to build up a clear picture.

Does anyone know where I could look to find an explanation which tries to give a reasonably detailed and clear picture of how it all essentially fits together?