No worries. I didn’t know how far you wanted to go with that. It doesn’t bother me any, and I realize it’s Apple’s fault in the end.

Don’t see it anymore on LastPass, but Safari doesn’t listen to the autocomplete tags unfortunately. [URL='http://stackoverflow.com/questions/22661977/disabling-safari-autofill-on-usernames-and-passwords’]Here’s a discussion on how to get around it[/URL], basically by adding a fake user/pass field that’s off the page.

If you have a password manager running, it may be filling in the AD user/pass fields with whatever you use to log into the website. Safari, at least, starting doing this with 1.0.1.

[quote=“Junkhacker, post: 28051, member: 21583”]Fog Configuration -> Fog Settings -> General Settings -> FOG_LEGACY_FLAG_IN_GUI[/quote]Ahh, nice! Thank you!

That error 2202 is returned directly from Active Directory, and from what I can tell after some searching, it’s saying “invalid username or group”. I’m not sure why it doesn’t like Administrator, but I would probably try a different user next. I would recommend using an account with less permissions anyway due to security concerns.

fog.log deletes itself when it gets to 10kb in size (quickly). Try stopping the FOG service, deleting fog.log, then starting the service. Check fog.log about a minute afterwards and you should see the error messages relating to the HostnameChanger.

I know to get it working for me, I had to change the global settings (to remove the domain from the username field) but that didn’t automatically change it for all my existing hosts. I added all my hosts to a group, and changed it through the group as well.

I’ve tried it out with a fresh install and it’s working for me. Maybe the new file isn’t overwriting the old one. I run into weird problems when updating a lot of times unless I delete the web directory (rm -rf /var/www/fog) before reinstalling.

I remember seeing a way to change it in 0.33 I think, but I don’t see it anymore. For any image not imported from a 0.32 database (i.e., manually added), it doesn’t seem to be possible to change the image type through the web interface. However, it can my changed manually through the server’s command line through MySQL, if you feel comfortable enough for that. Here’s how:

[code]mysql -u root (also add -p if you have a password)
use fog;
update images set imageLegacy = 1 where imageName = ‘Name of your image’;[/code]

It depends on if you wanted to store the file contents in the database in an encoded format. I only mentioned this because before revision 1724 updates.php was trying to decode it when retrieving the file but FOGConfigurationPage.class.php never encoded it when it saved it.

As of revision 1726, the file is not encoded when its stored, but it is decoded when it’s retrieved, so it corrupts the file. Either FOGConfigurationPage.class.php lines 544 and 552 will need to encode the data before it’s stored, like:
[code]->set(‘file’,base64_encode(file_get_contents($_FILES[‘module’][‘tmp_name’][$index])));[/code]

or updates.php line 20 will need to have the decode statement removed from it:
[code]print $ClientUpdate->get(‘file’);[/code]

but only one of those options. Sorry for the confusion!

Thank you very much, Tom.

I made the following edits to lib/pages/FOGConfigurationPage.class.php on lines 544 and 552 and the file now successfully saves to the mysql database. For a new module, it was saving the temporary filename to the database as cuFile. When updating an existing module, basename() would cut off most of the uploaded data. The data isn’t encoded, so if you want that you’ll need to add the decode function back into service/updates.php line 20.

I’ve tested it and it’s back to working perfectly! Thanks again.

[CODE]diff ~/fog_r1724/packages/web/lib/pages/FOGConfigurationPage.class.php lib/pages/FOGConfigurationPage.class.php

544c544
<->set(‘file’,basename(file_get_contents($_FILES[‘module’][‘tmp_name’][$index])));

->set(‘file’,file_get_contents($_FILES[‘module’][‘tmp_name’][$index]));
552c552
<‘file’ => basename($_FILES[‘module’][‘tmp_name’][$index]),

‘file’ => file_get_contents($_FILES[‘module’][‘tmp_name’][$index]),[/code]