Talk:Beginning Administration 1 FAQ

Revision as of 16:44, 2 July 2010 by Helen Foster (talk | contribs) (Can we re-name this page: reply)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Note: You are currently viewing documentation for Moodle 1.9. Up-to-date documentation for the latest stable version is available here: Beginning Administration 1 FAQ.

If you have something to contribute please feel free.

If there is anything here you disagree with, please add in another perspective.

If the language is too opaque then make it more simple, which makes it easier to read.

Can we re-name this page

to "Beginning Administration 1 FAQ" so that it appears in order with 2,3 and 4 in the index?

Thanks for your suggestion. It's done! --Helen Foster 16:44, 2 July 2010 (UTC)

Why am I just not getting how Permissions and Roles work?

This section really jumps around in my logic and needs more links. The intro is good because it addresses a problem I had/have :) But after that I would delete the rest. At a certain point the words revert to a description of a process, where authentication is mixed in with front page roles and terms of teacher, course creator and such and what happens when a user comes back from a course..... I think more links will help and maybe ask another question (or more) to focus upon why the mental block about permissions, contexts, capabilities, and roles. --chris collman 12:37, 20 July 2009 (UTC)

Yes, you are probably right Chris, but my initial concern was to get the question up. Just go for it, I am not in the position I can spend a lot of time doing this until the end of September now. Cheers..

General comments on page

Hi Colin. Just a couple of quick thoughts as I scan the FAQ -which is really good! - in the My Moodle's broken section might it be worth mentioning that sometimes sites break because they've been hacked? Perhaps adding a link to one of the forum posts on how to diagnose a hacked moodle? Not wishing to put admins off but to be on the safe side. Also: in the logo section - it might be worth mentioning that if you want a quick solution just use the standard logo theme where you can upload your own logo to site files rather than having to ftp? Mary--Mary Cooch 14:26, 12 August 2009 (UTC)

Hi Colin and others. This page has some great stuff in it. Be careful (or not :) ) with information that is very Moodle site specific. Getting content up is good. Placing content that does not work for a beginning administrator is not good.

In general, we need to be careful about presenting examples as facts, especially to a beginning administrator. For example, the Moodle2 theme header in is 200px × 46px and is located /theme/moodle2/pix/moodle-logo.gif. This is different from the Formal White logo in both size and generic location. The warning about the height was spot on but it ignored another common error "all Moodle sites work just like my site".

I do want to point out that placing FAQs in MoodleDocs is a big positive and having a FAQ and not putting it up is a negative. A collaborative project like MoodleDocs is all about taking good ideas (this is a FAQ) and tweaking them over time by the collective knowledge. I am talking about tweaking.

Thanks to all the past and future contributors to this series of FAQ pages. --chris collman 12:41, 5 August 2009 (UTC)

To make things a little more coherent (possibly), some questions have been shifted to the Beginning_Administration_2_FAQ page and some from there have been brought here. --Colin Fraser 15 August 2009.

Should I use a test site to try things out

Colin Fraser recently added the 'Should I use a test site to try things out' item to the FAQ. While I agree with most of what he says, I have to disagree with the "for most circumstances, the Windows Xampp installer is the best for a Windows environment" statement. In my opinion, a development/test instance of Moodle should be setup in the same way as the production site, using the same version of the database, web server and Moodle installation package. This ensures that whatever problems you might encounter on the production site can be reproduced on the development/test site when you need to troubleshoot.

This is a valid point, and I am forced to agree. My thought at the time was to create something quick and dirty - but why did you not just add that thought, or edit the response. Colin Fraser 08:41, 12 December 2009 (UTC)Colin Fraser.