I’ve spent hours this morning trying to figure out how to globalize a “sign in” link for my test site… i’m using MT 4.21-en (open source) and NOT one of those professional website templates (rather just a modified stylesheet of mine)…
i wish i could figure out how to make a user sign in without having to re-sign in again when switching to a separate blog on my site….i tried putting the sign-in widget in the global templates section and thought that would work…it didnt…after logging into the home page, when clicking another link to another blog, rather than seeing my screenname there, it says “sign in” again!
can anyone PLEASE help me with this? (i even tried using the “sign in” template from the professional website templates widget set and that didnt work either).
thank you!
Reported on Movable Type 4.2
MT should be able to get you close enough to this if you make your users do a sign-in with a Movable Type user account on your blog. If they choose to have MT "remember" their login when they sign in the first time, it should keep the cookie there and all they have to do is hit the sign-in link on a comment section on any of your blogs to be transparently authenticated on that blog.
alright, so basically you're saying there is no professional solution to having just one sign-in page between blogs.... for instance, here is my test page: www.u2station.com/index2.php ..sign in at the top right corner... and then click the news tab www.u2station.com/news2/index.php ...as you can see, at the top right hand corner, you have to sign in again... it just makes it seem unprofessional, thats all. darn it.
Use the SingleCommunity config directive. All blogs are treated independently otherwise.
thanks...but when i tried putting this into the config-mt.cgi file, i ended up having a MAJOR disaster...apparently i used the "original" config-mt.cgi file and had to re-write in the database names/password/paths manually....then i experienced a slew of errors....then i couldnt figure out where the sqlite file path was at...i panicked...then i backed up my database....then i uploaded another new config-mt.cgi file and a screen came up instead saying to "initialize database" for a new user...and i did..and i LOST MY ENTIRE DATABASE! and then when i tried restoring it, nothing worked...
so now i'm left manually remembering/putting in my entire customized templates again...luckily i have all my images and stylesheets backed up...but not the template modules and widgets i installed.
what a disaster....all for putting in a single line: SingleCommunity 1 . what did i do wrong???
If you restore the state of the MT files to before you set it to SingleCommunity 1, your old database should work. Could you be more specific about "nothing worked?" Were you able to see the Dashboard?
mike, thanks for your suggestion...believe it or not, the following night i downloaded version 4.23 of MT and installed a fresh copy on my server...and i re-wrote out all the template modules (also copying them from archived/cached php pages via viewing its source code)...and i'm back to normal now...
i re-traced my problems all the way back to that fateful incident of editing the "mt-config.cgi-original" file, renaming it to "mt-config.cgi" and uploading it...i basically edited the wrong config file! and thats how it all went down in disaster. THIS TIME, i edited the correct config file, typed in the SingleCommunity 1 line and uploaded it...it works perfectly now! and on a fresh install of movable type 4.23 on top of that.
just want to warn others of making sure not to repeat my same mistakes (well, on top of that, i did this at 4am and i guess my brain wasn't working 100% either).
You might want to switch to MySQL or PostgreSQL. Speaking as a MySQL user, preparing for an upgrade is really easy. I just log into my host by ssh and run zip on my MT folder, and mysqldump on my database. That gives me a zip file of my current installation, and a SQL file that contains all of the SQL commands needed to build a new copy of my database if the old one gets damaged. MySQL and PostgreSQL also have the advantage of being run as separate servers on the network, with lots of security, so you have a separation between the files in your home directory and the database.
actually i am using mysql in my cpanel...i ended up trying to edit the original config file and didnt realize that "sqlite" is redundant for my purposes...i simply use phpmyadmin to log into mysql databases...but since im not a database programmer, i need to avoid screwing around with anything in there (even doing a query or adding new table content for a new module to me is out of my league).