MODX Staff
Yes, you are correct, when creating a new user it automatically sets template in user settings to "Default" and that overrides what I’ve choosed as manager theme.Okay, that needs looking at then. It should set it initially to whatever the current configuration setting is for the theme - obviously, that hasn’t happened in your case.
Yes, that is a really good idea garryn. No reason to set manager settings if they didn’t really specify anything.
Also, the question of setting defaults for the settings is open for discussion because when the default is set, it will always save that value (which may not be desired). Perhaps, leaving all the user settings blank and only save them if a value is physically set is the way to go.
Thoughts anyone?
Or, if you’re less patient and not SVN knowledgable, you can get patches from our Trac site connected to SVN. For instance, go to http://mirror1.cvsdude.com/trac/rethrash/tattoo/log/tattoo/trunk and you’ll see a list of the latest revisions.Wow, that was interesting and usefull! I will never more need to ask stupied questions about solved issues!
MODX Staff
also when they log into the manager none of the styles, images, icons appear... The manager is totally corrupt. I’ve cleared the site cache but still nothing.Check what manager theme setting the user has been assigned in the user settings. It’s a known issue in beta 3 (and will be corrected in the next beta) that users are being set the ’Default’ theme when they are saved unless specified differently. Change the theme to ’MODxLight’ and that should solve that issue.
Not sure on the QuickEdit stuff at the moment.
MODX Staff
Thanks for the fix... will be committed soon.
Bug description: in top frame of MODx Manager with MODxLight theme there are green tabs. Active tab has at the bottom of it a row with some buttons. The width of this row in Mozilla (1.5.0.7) and Opera (9.0.1) is a full browser window width, but in IE 6 (6.0.2600.0000) sometimes
MODX Staff
We certainly welcome close scrutiny in IE this early. There’s lots of small details that are in flux in the manager right now, and we typically get everything finalized in FF prior to making IE work. Please don’t hesitate to keep after us to fix IE earlier though, and DEFINITELY keep fixes coming with the reports! Thanks so much for your assistance.
If nobody from developer’s team browses the web with IE 6.0 and than doesn’t check MODx in that browser, I understand this: I also does not use IE by myself, I like and use Opera 9... But IE 6 is still the dominant browser among other internet users, so I must to be sure than great and lovely MODx CMS will work for them! I still be new to MODx, by I’m not new in the "art" of fixing Internet Explorer (and other browsers) bugs. So I propose to test next MODx stages in IE 6 and, in the case of the need, to fix them.
This discussion is closed to further replies. Keep calm and carry on.