Blaze 0.90 Login Problems - Fixed
OK guys, there were a few of you having login problems…
Well, I’ve fixed them now. Just download the latest release, and make sure you clear out your database and execute the new SQL.
The new code creates your first user on first login, and the encryption is now handled by CI’s encryption class to make sure that it works across different platforms and environments.
There’s also now a critical fix to the simplepie library, which was previously breaking the admin dashboard on some versions of PHP.
Please download the very latest release and comment with any bug reports or praise 
Elliot
If you enjoyed this post, make sure you subscribe to the RSS feed!
1. In First login page, I entered “admin” for username, “test” for password. Then users table created like this
admin - a94a8fe5ccb19ba61c4c0873d391e987982fbbd3 - active
but I cannot login.
2. .htaccess configured. for http://localhost/blaze
Lines:
RewriteBase /blaze
RewriteRule ^(.*)$ http://localhost/1/ [R=301,L]
Ok, first up, set your htaccess to this:
Then, make sure you’ve got the very latest package. There was a critical problem in the simplepie library that breaks the admin dashboard page.
Now, try to login, see what happens.
If it ‘looks’ like it doesn’t work, try opening http://localhost/blaze/admin/page/ in your browser, to see if the login actually worked, but the redirect or dashboard failed.
Elliot
Still cant login, well it actually logins, but looks like after redirect it looses session or something. And if i set sess_use_database = TRUE, it creates plenty of records whit different session_id, instead of updating only one record. And by the way, you should add blaze_session table to you`re sql scheme, so that people would not have to create it.
Ok, Fount the problem whit login and session,
You need to change
$config[’cookie_domain’] = “.”.$_SERVER[’HTTP_HOST’];
to
$config[’cookie_domain’] = “”;
yes, i have same problem too..
I dont know maybe its meant that way, but in admin->navigation, it sorts navigation backwards. For example i set it Home, Blog, About, after refresh it shows About, Blog, Home.
O, and one more thing, you need to change
$config[’log_path’] = APPPATH.’logs’;
to
$config[’log_path’] = APPPATH.’logs/’;
or logs will not be saved in logs folder, instead they will be in APPS folder whit logslog-2008-03-11.php name.
Hey staze… thanks for all the comments.
I’ll look into all of these issues.
Elliot
With these changes login form working ;
.htaccess
RewriteBase /blaze/
RewriteRule ^(.*)$ http://localhost/blaze/1/ [R=301,L]
config.php
$config[’cookie_domain’] = “”;
$config[’log_path’] = APPPATH.’logs/’;
Seyhun’s post above worked for me also. Thanks.
Thanks for that, the 0.90 zip now includes this fix.
Elliot
Hi, just wanted to let you know I logged in successfully, it looks amazing, I’m really looking forward to future versions, keep up the good work.
I think the problem I was having logging in was, my database collation was latin, I never set the database to utf_general_ci when I first created it.
Might be a problem others are having.
Потестим. Спасибо за вашу работу..
Work Perfect on my Side
waiting for next released…
Elliot, no problem, i am glad to help.
-It would be nice to have some kind of module manager, where i could see if there are any new versions of modules, and see current version, author, be able to turn it off, so that only admins could have access to this module.
- And it would be nice to be able to see info about module as a normal user, something like blog/author would show blog module author information.
P.S. Hope to see new releases soon.
Excellent! I can’t wait to play with this.
A couple of quick suggestions though:
- A proper bug tracking would be great, so both you and we, the users, can keep track (pun intended :P)
- Don’t include CI with the package. Not only will you run in to license problems (especially if you go GPL or similar), but it is just too big. I have a “global” install and run off of one system directory (or rather, will …), so it is kinda useless for me to redownload what I already have.
I’m sure I’ll have more later once I get to playing, but looking good!
Okay, I have more.
CREATE TABLE IF NOT EXISTS `blocks` (
`id` int(11) NOT NULL auto_increment,
`area` int(11) NOT NULL,
`theme` varchar(50) NOT NULL,
`template` varchar(50) NOT NULL,
`module` varchar(50) NOT NULL,
`method` varchar(50) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=68 ;
–
– Dumping data for table `blocks`
–
INSERT INTO `blocks` (`id`, `area`, `theme`, `template`, `module`, `method`) VALUES
(67, 2, ‘default’, ’single_column’, ”, ”),
(66, 1, ‘default’, ’single_column’, ‘blog’, ‘latest_items’);
1. I think it’d be nice to not force users in to a given engine. Not all users have the specified engine installed (Of course, MyISAM, but I’m talking about if you used a different engine.
2. Take out the AUTO_INCREMENTS. It makes things messy in my opinion. Default data, IMO, should begin with 1 and be sequential. There’s another table I saw that started with 1, jumped to 5, and the next increment was set to 6.
Back to playing.
In case anyone else has this issue, I installed Blaze 0.9 and made the appropriate changes to .htaccess and database.php.
I was getting “Unable to locate the model you have specified: blog” errors until I enabled PHP5 on my server.
Wow, and Hi everybody!
Thank you all for the comments and feedback, it’s great to see that everyone has ideas and opinions on how to make Blaze a really great system.
I just want to say, that there will be about 6 more weeks of releases and upgrades, and then we should be at a basic 1.0 version.
At that point, I’ll put up a bug-tracker and a few other things to get development rolling.
As I’ve said in the past, Blaze is still very much just a ‘proof-of-concept’ and needs a great deal of work, but I’m glad that there’s plenty of support behind this projet, and it’s really encouraging me to keep building it.
Elliot
Nice work! Thanks for all these great ideas and lines of code, Elliot!
I’ve examined your files to see how blaze works. Excellent concept!
But I can’t use blaze so far, because I’m running into error “No input file specified” as soon as I’m calling a subcontroller like /about.
The startpage is working but any link leeds to the error “No input file specified”.
I think it’s a .htaccess-issue?! But how can I solve it?
My .htaccess: (blaze is installed in the root)
RewriteEngine On
RewriteBase /
# Must do this before a trailing slash gets put on it
RewriteRule ^static/frontend/([a-zA-Z_-]*)/(.*)$ application/views/themes/$1/static/$2 [L]
RewriteRule ^static/admin/([a-zA-Z_-]*)/(.*)$ application/views/themes_admin/$1/static/$2 [L]
# Add Trailing Slash (Force it!) - It looks cool
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !(.*)/$
RewriteRule ^(.*)$ http://localhost/1/ [R=301,L]
# Admin ‘dashboard’
RewriteRule ^admin$ index.php/admin [L]
RewriteRule ^admin/$ index.php/admin/ [L]
# Admin functions within Admin module and controller
RewriteRule ^admin/(navigation|users|settings|login|logout)$ index.php/admin/$1 [L]
RewriteRule ^admin/(navigation|users|settings|login|logout)/(.*)$ index.php/admin/$1/$2 [L]
RewriteRule ^admin/nav_(.*)$ index.php/admin/nav_$1 [L]
# All others, push to the module in question
RewriteRule ^admin/([a-zA-Z]*)$ $1/admin [L]
RewriteRule ^admin/([a-zA-Z]*)/(.*)$ $1/admin/$2 [L]
# Any request were the file or directory doesn’t exist…
# Push to CI
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php/$1 [L]
Maybe you should make a bug report page for us…
P.S. You shouldn’t allow to direct access (non POST) for this /admin/nav_ajax_reorder/ etc. functions.
BTW. If you would like to have polish language translations, feel free to let me know
Sorry, I just read what you wrote about bug-tracker above…
Sorry, forgot to tell you that I’m using PHP5 von Apache as a CGI. Maybe this helps.
If you’re running PHP as CGI and not as an apache module, you should try adding “cgi.fix_pathinfo = 0″ to your php.ini if you’re getting the error “no input file specified” mentioned above.
That works for me and I’m happy that I can use blaze now!
i wanna a Multi-language website. how i can do with Blaze?
We need forum ;]
Hi guys,
I’ve found a little mistake in the .htaccess file. Seems someone has forgotten a directory in the first directive:
# Must do this before a trailing slash gets put on it
RewriteRule ^static/frontend/([a-zA-Z_-]*)/(.*)$ application/views/themes/$1/static/$2 [L]
RewriteRule ^static/admin/([a-zA-Z_-]*)/(.*)$ application/views/themes_admin/$1/static/$2 [L]
Should be:
# Must do this before a trailing slash gets put on it
RewriteRule ^static/frontend/([a-zA-Z_-]*)/(.*)$ system/application/views/themes/$1/static/$2 [L]
RewriteRule ^static/admin/([a-zA-Z_-]*)/(.*)$ system/application/views/themes_admin/$1/static/$2 [L]
Otherwise the Theme resources won’t be properly loaded and you get a freaky white -nonetheless working- Blaze frontpage
Glad to be of service! Greets n kudos
Maybe to clarify: I added the “system/” before “application/” in both lines.
[Praise] First off, well done with the build thus far! Definetly a stellar start to what I believe will be an excellent CI CMS [/Praise]
As far as issues, I can access each page individual by re-writing the uri, however when I click successive links, multiple trailing slashes are added in place of the index, breaking an second page of its content and styles.
Any thoughts? I couldn’t find the problem and I imagine it is an htaccess issue or perhaps my php configuration, but I was wondering if anyone else experienced a similar issue?
wow.. it really looks great..
Hope to see new releases soon..
Works well after switching PHP5 on.
Nice start, Elliot. EE lite!
And here is my 50 cents I find some trouble installing Blaze on my web hosting.
I receive error can load model page but after I switch to PHP5 now is OK.
But there was problem when I try to access blog or admin page.
Here is my modification of .htaccess notice ? after index.php this is the key.
I also read that adding ? after index.php solve problems with code igniter and dreamhosting. Here is .htaccess
#This is optional
AddHandler x-httpd-php5 .php
Options Indexes FollowSymLinks
RewriteEngine On
RewriteBase /
# Must do this before a trailing slash gets put on it
RewriteRule ^static/frontend/([a-zA-Z_-]*)/(.*)$ application/views/themes/$1/static/$2 [L]
RewriteRule ^static/admin/([a-zA-Z_-]*)/(.*)$ application/views/themes_admin/$1/static/$2 [L]
# Add Trailing Slash (Force it!) - It looks cool
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !(.*)/$
RewriteRule ^(.*)$ http://yourdomain.com/1/ [R=301,L]
# Admin ‘dashboard’
RewriteRule ^admin$ index.php?/admin [L]
RewriteRule ^admin/$ index.php?/admin/ [L]
# Admin functions within Admin module and controller
RewriteRule ^admin/(navigation|users|settings|login|logout)$ index.php?/admin/$1 [L]
RewriteRule ^admin/(navigation|users|settings|login|logout)/(.*)$ index.php?/admin/$1/$2 [L]
RewriteRule ^admin/nav_(.*)$ index.php?/admin/nav_$1 [L]
# All others, push to the module in question
RewriteRule ^admin/([a-zA-Z]*)$ $1/admin [L]
RewriteRule ^admin/([a-zA-Z]*)/(.*)$ $1/admin/$2 [L]
# Any request were the file or directory doesn’t exist…
# Push to CI
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?/$1 [L]