- Last Active
- Preferred Name
Hello, for once we are ahead of the game! We added this a number of years ago for the exact reason that Sandra mentioned, which is to allow staff to update their own data. It works through the Update Personal Data_family permission, which can be assigned to roles of category student. Well, that was easy ; ) Ross.
Hi i9learning, we don't mind if you remove the image, but please do keep the copyright and credit information in the footer. To remove the icon I suggest you edit /index.php, and remove the following line from near the end of the file:
This is a bit of a core hack, and will be overwritten when you update, so you'll have to redo it.
Later this afternoon I'll move the style for this into the theme, so that it can be removed at the theme level.
Hi Ayu, it looks like you've caught a bug of some kind, which we can hopefully track down fairly soon. This report is one of @sandra's contributions, and so for the sake of expediency I'll see if she can answer this one for you. I know that she is away at the moment, but will be back soon. Sit tight, and we'll get an answer to you in the coming days.
Hi @sandra, if you can't find time to look into this, let me know and I'll take a look. Thanks, and I hope you had a great trip : ) Ross.
Hi Lucas, thanks for sharing all of this background about yourself and your ideas. A lot of your thinking sounds exciting, cutting edge, and exactly what education needs. I guess my question would be (and this has been asked of me many times), why start your own project, when there are others to join? My reason for asking this question is that you've found Gibbon at a unique time, as we transition from a legacy codebase to something much more modern. @sandra is leading this work, and we are very much looking for programmers to join us, to help with the work itself, but also to begin offering input on different directions we might take longer term. Our current focus is on completing an object oriented refactoring of the codebase: forms are 98% done, tables are next, and then we will move on from there. The aim is to reproduce the existing functionality (which is fairly extensive) in a far more modern, scalable and maintainable form.
Your API point is extremely interesting, not least because I've spent a lot of my life moving data around between various school systems. If you take a look at our Extend page, you'll see a module called Meet The Teacher, which has a partial-API designed to allow Gibbon to talk to a specific online system (http://www.meettheteacher.com). This has worked brilliantly, allowing Gibbon schools to have their data seamlessly synced into a third party system. I see this as an excellent first step towards an eventually more powerful and configurable API.
We'd love to have you join us, should you be willing to roll up your sleeves and get your hands dirty with some legacy code. Cheers, Ross.