webman

Hi Dave Sorry you encountered that problem! The passwords are currently just stored using a SHA1 hash, so you should be able to do this within phpMyAdmin - just choose sha1 from the field function dropdown list. If that doesn't work, run this bit of SQL: INSERT INTO `users` (`user_id`, `school_id`, `department_id`, `username`, `firstname`, `lastname`, `email`, `password`, `authlevel`, `displayname`, `ext`, `lastlogin`, `enabled`, `created`) VALUES (NULL, 1, 0, 'admin', '', '', '[email protected]', '5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8', 1, 'Administrator', '', '2014-01-08 22:02:00', 1, '2014-01-08'); It will create a user with a username of admin and a password of password.

Excellent! How did you find getting off it at the start of your fast - did you come down gradually before, or just put up with the caffeine withdrawal headaches until they went?

Someone posted this on another forum I use

Thanks fiza Sadly not - I haven't had any time lately to work on this Ah! OK. If you add a semicolon after your commands, it should be fine. For example: CREATE DATABASE printmaster;

Hi eskIT. What errors are you receiving when you try to make the database? How are you trying to do these? When you set up MySQL, you should have set a "root" password at some point. When you log in as root with that password, you should be able to do anything - including creating new databases.

Thanks to those who have offered help here with regards to MSSQL The database libraries I use in PrintMaster, in theory, support multiple databases - but the queries have to be written in a slightly different, generic, way. For most of the project I think that would be fine - but there are several queries in there at the moment that use mainly MySQL-specific functions and syntax, which would need to be updated. So - if MSSQL was something that people really wanted to be supported, I could look into the possibility of updating the project to support it "out of the box". The only problem is that I don't know much about using MSSQL at all Do I just download SQL Server Express and away I go?

Again, it depends. Mainly on three factors - how long they've been on green (if known), how far I am from approaching them, and the layout (direction of approach & exit). If I have a good chance of getting through them safely in time before them changing, I will maintain or increase speed when possible. If it's unlikely I'll get through this time, I'll maintain or lower my speed so that when they do turn green, it's an efficient process. Essentially, the goal here is to try and keep moving but without coming to a complete stop. To me, it's not a black and white situation of either just speeding up or slowing down - all other things that you need to consider when driving (weather conditions, visibility, driver skill, vehicle conditions, other road users and so on), also need to be accounted for.

Thanks dcorwin822, that sounds like a useful feature as well. Added to the list

phpMyAdmin can be a bit cumbersome to set up and get working properly if you don't spend time trawling through the docs. And even then, sometimes it doesn't play nice! Instead, I'd recommend a light-weight alternative, Adminer. (Direct download for MySQL English-only version). It's a single file - just drop it into your web-accessible folder and access it through a web browser. You can then enter the details to log in - server will probably be localhost, and then the database, username & password you already have (by the sounds of it).

That sounds pretty cool

The issue there is that the frequency range you're referring to is no good for TV or mobile phones/data.

Great collection of photos. Speaking of Brooklands, did anyone see the Scalextric world record attempt that was part of James May's series of programmes?

Added it to the list @fiza

It looks like you don't have the cost fields in the database. Have you ran /upgrade.php in your browser straight after installing?

Thanks eclass! Glad you like it

Hi dcorwin822. Thanks very much for trying out PrintMaster and providing some great feedback and suggestions. I'm really glad you've found it useful. I'll take note of your comments and hopefully incorporate some, if not all of those in future versions

That's alright I only just added that step to the instructions this weekend. Will hopefully help others installing it for the first time.

For new installs, you have to visit upgrade.php in your browser first. This should ensure the default database is up-to-date with all changes. When you've done that, it should work fine

Cooool

It will be in the 'events' table. The date fields should be readable. You can find the ID of the printer in question by going to the Printers page, click the Edit link on the one that it was wrongly installed to, and look at the address bar at the last bit that says "id=X" where X will be the ID number.

For now, I'm afraid you'll have to delve into the database using phpMyAdmin/HeidiSQL to alter or delete the log entry.

Hi Pete. A departments feature has always been on the TODO list, but have never really gotten round to adding it. Might do that very soon as well to keep the momentum up

It can now, yes. Consider it done! Download v1.3.0 (includes fix for consumable costs and added purchase date & cost to printers). Don't forget to read upgrade/changes files. In response to the costs in the report section. The cost is stored with each log entry at the time, to account for variation in consumable costs over time. E.g. log an install when a consumable is £40, the log entry will be £40. If you then change the consumable cost to £50, previous log entries will remain at £40. This is just to ensure that they always remain accurate, regardless of any changes. If you need to update your logs for that expensive consumable, I would suggest just updating that manually yourself after upgrading to the latest version. The cost columns should now all be float(6,2).

D'oh! Soon