Login add-on installation help

Permalink
I uploaded the 'Login' add-on directory to the 'Packages' directory and hit installed but I get this error...

LoginBlockController not found. Please check that the block controller file contains the correct class name

Any suggestions?

 
frz replied on at Permalink Reply
frz
what version of concrete5 are you running?

it says in the upper right corner of the dashboard when you first get into it.
hpatel replied on at Permalink Reply
version 5.3.2
frz replied on at Permalink Reply
frz
5.3.3.1 is out, that might help
hpatel replied on at Permalink Reply
thank you.. i'll try that out
hpatel replied on at Permalink Reply
An Unexpected Error occurred while upgrading: mysql error: [1062: Duplicate entry '1-1' for key 'PRIMARY'] in EXECUTE("ALTER TABLE FileAttributeValues DROP COLUMN fakID")



:(
frz replied on at Permalink Reply
frz
hpatel replied on at Permalink Reply
Not really a solid answer on there. I tried the upgrade last week right before 5.3.3.1 was released and came across the same error, I had read that page for suggestions.
frz replied on at Permalink Reply
frz
From the very end of that thread....



Solution for Duplicate Key Error on 5.3.3 or 5.3.3.1 Upgrade
Oct 08, 2009 at 6:28 PM
An Unexpected Error occurred while upgrading:
mysql error: [1062: Duplicate entry '1-1' for key 1] in EXECUTE(
"ALTER TABLE FileAttributeValues DROP COLUMN fakID"
)

If anyone gets this duplicate key error it's caused by these renamed attribute tables:

_CollectionAttributeKeys
_CollectionAttributeValues
_FileAttributeKeys
_FileAttributeValues
_PageSearchIndexAttributes
Viewing 5 lines of 7 lines. View entire code block.

_CollectionAttributeKeys
_CollectionAttributeValues
_FileAttributeKeys
_FileAttributeValues
_PageSearchIndexAttributes
_UserAttributeKeys
_UserAttributeValues


So, if you're making a second attempt at an upgrade and you restore your original database make sure that those tables don't exist after your database is restored.
hpatel replied on at Permalink Reply
_CollectionAttributeKeys
_CollectionAttributeValues
_FileAttributeKeys
_FileAttributeValues
_PageSearchIndexAttributes
_UserAttributeKeys
_UserAttributeValues
ryan replied on at Permalink Reply
ryan
Yeah, remove those tables - assuming that you have a backup of your database. If you don't have a backup yet, backup first, then remove them.

Once they're gone - hit the upgrade script.
hpatel replied on at Permalink Reply
I tried that and got this error..


An Unexpected Error occurred while upgrading: mysql error: [1050: Table 'collectionsearchindexattributes' already exists] in EXECUTE("CREATE TABLE CollectionSearchIndexAttributes ( cID INTEGER(11) UNSIGNED NOT NULL DEFAULT 0, PRIMARY KEY (cID) )")

should i remove the collectionsearchindexattributes table and do it again?
ryan replied on at Permalink Reply
ryan
Delete:
CollectionSearchIndexAttributes
FileSearchIndexAttributes
UserSearchIndexAttributes
hpatel replied on at Permalink Reply
this looks like a new one...

An Unexpected Error occurred while upgrading: mysql error: [1062: Duplicate entry 'exclude_sitemapxml-1' for key 'akHandle'] in EXECUTE("insert into AttributeKeys (akHandle, akName, akIsSearchable, akIsSearchableIndexed, akIsAutoCreated, akIsEditable, atID, akCategoryID, pkgID) values ('exclude_sitemapxml', 'Exclude From sitemap.xml', 1, 0, 0, 1, NULL, '1', 0)")


thanks for the help!
ryan replied on at Permalink Reply
ryan
Is there any way to restore your 5.3.2 database, remove those tables prefixed with the underscore, then try again. Ideally you'd use a db that didn't get upgraded by the 5.3.3 branch, but that may not be possible..
hpatel replied on at Permalink Reply
I backed up the 5.3.2. database before I started the whole process.
hpatel replied on at Permalink Reply
An Unexpected Error occurred while upgrading: mysql error: [1054: Unknown column 'ak_exclude_nav' in 'where clause'] in EXECUTE("select distinct p1.cID, if(p2.cID is null, pt1.ctHandle, pt2.ctHandle) as ctHandle from Pages p1 left join Pages p2 on (p1.cPointerID = p2.cID) left join PageTypes pt1 on (pt1.ctID = p1.ctID) left join PageTypes pt2 on (pt2.ctID = p2.ctID) inner join CollectionVersions cv on (cv.cID = if(p2.cID is null, p1.cID, p2.cID)) left join CollectionSearchIndexAttributes on (CollectionSearchIndexAttributes.cID = if (p2.cID is null, p1.cID, p2.cID)) where 1=1 and cvIsApproved = 1 and (p1.cIsTemplate = 0 or p2.cIsTemplate = 0) and ak_exclude_nav = 1 and (p1.cID not in (5,6,7,8,9,12,13,14,15,16,17,18,19,20,21,22,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,101,103,104) or p2.cID not in (5,6,7,8,9,12,13,14,15,16,17,18,19,20,21,22,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,101,103,104)) ")
hpatel replied on at Permalink Reply
I got that error, but I am able to load the website and it shows version 5.3.3.1
ryan replied on at Permalink Reply
ryan
ugh, that was rough...
Run the search indexer in the maintenance section & then check out your site & see if it made it though intact..
hpatel replied on at Permalink Reply
Looks like the upgrade worked.. thanks for the help Ryan.

I tried to install the login add-on again and got the same error..

The following errors occurred when attempting to process your request:

* LoginBlockController not found. Please check that the block controller file contains the correct class name.
ryan replied on at Permalink Reply
ryan
so, you should have:
/site_root/packages/controller.php
/site_root/packages/blocks/login/controller.php

so, open up the block's controller & make sure it looks good (not corrupt) and that the class that's missing exists.
hpatel replied on at Permalink Reply
Unless i'm missing something. Does this mean that the class exists?

class LoginBlockController extends BlockController



there is no mention of LoginBlockController in the packages/controller.php file.
hpatel replied on at Permalink Reply
The admin says 5.3.3.1 on the side.

but on the admin homepage i see this message...

You have downloaded a new version of Concrete5 but have not upgraded to it yet. Upgrade your site to 5.3.3.1 now!
dealerpriest replied on at Permalink Reply
I've got exactly the same problem.

I've tried to just visit the blocks/login/controller.php and the browser outputs:

registerText) $this->registerText=t("Click here to register »"); } function view(){ $this->set('registerText', $this->registerText); $this->set('showRegisterLink', $this->showRegisterLink); $this->set('returnToSamePage', $this->returnToSamePage); } function save($data) { $args['registerText'] = isset($data['registerText']) ? trim($data['registerText']) : ''; $args['showRegisterLink'] = intval($data['showRegisterLink']); $args['returnToSamePage'] = intval($data['returnToSamePage']); parent::save($args); } } ?>


Very strange! It seems that php suddenly stops parsing the controller.php and spits the rest of the file to the browser.

Anyone got any ideas?
micr0 replied on at Permalink Reply
Just FYI in a fix for this problem. Ensure that short_open_tag is on in the php.ini file. Took a while to find the solution to this problem, but enabling short tags stop the parsing halfway and installed properly.