password element in conflict with database

Status
Not open for further replies.

8ight

New Member
Hi everybody,

I encounter a little problem with the password element.



In my database, the password is in varchar(100).
The password element try to change it in TEXT.



With the conflict, nothing works (error 500).
If i change to TEXT in the database, same issue (error 500).

Editing the password element plugin doesn't show any tweak to avoid the problem.

My question is: how can I change the password element to varchar(100) instead of TEXT ?

joomla 2.5.9
fabrik 3.0.6.2 updated with GitHub for 2 or 3 days.

Thanks.
 
Edit you list, in "Advanced" set "Alter field types" to NO or New only.
Then fabrik won't change the database table column types.
 
that's exactly the configuration of my list. With this configuration, it's not working because joomla needs the password column configured to TEXT, fabrik doesn't work because it needs varchar.

I changed to "yes" on my screenshot only to figure out what fabrik was trying to do to the table.
 
All my fabrik passwords (old and new ones) are varchar(length-of-"Field-length") in the database.
Did you do a complete GitHub update (no "selection" of plugins)?
 
(I have inverted TEXT and varchar in my last post, it's joomla who is set to vachar and my fabrik password element plugin set to TEXT)

At first, i just took what I needed, but since that, I have installed the complete package provided via GitHub.

My joomla keep saying updates are available for fabrik time to time. I keep it up to date.

I'll try tomorrow to uninstall and re-install the plugin. For now I don't understand why it ask for TEXT (search for it in the code, but I'm not so good with PHP).

EDIT: i just tried, still the them.
 
Ok, I have just followed this tutorial, with a fresh GitHub downloaded file:

- in the manage tab, component_fabrik appears at version 3.0.6.2;(ignore this, it's the admin part, the package is at 3.0.6.3)
- nothing appears in the update tab.
- same problem with password element plugin.
 
After a GitHub update + "Refresh Cache" on all fabrik elements in ExtensionManager/Manage ALL fabrik entries must have version 3.0.7 and Date ${createdate.
Otherwise the GitHub files have not been copied correctly.

But I beside of this I don't know where TEXT on password elements should come from: in all my Joomla installations (old and new ones, fabrik2 and fabrik3) password elements are created as varchar columns in the database.
 
Fabrik Module - Tag Cloud Site Module 3.0.0 May 2006
Fabrik Package Site Paquet 3.0.6.3 September 2012
Fabrik Administration Composant 3.0.6.2 September 2012
everything else is: version 3.0.7 and Date ${createdate}

the comment on this tutorial shows that I'm not the only one experiencing this issue. But I don't get it, why fabrik wants the joomla system password column to be TEXT ?
 
This has to be 3.0.7
Fabrik Administration
Composant 3.0.7 ${createdate} Fabrik


Tag cloud module is old, is this a migrated Joomla1.5/fabrik2 site?

I would suggest to download the actual fabrik3.0.6.3 compnent (All in one installer package) from http://fabrikar.com/downloads (http://fabrikar.com/downloads/details/36/425),
install the zip,
update from GitHub again,
refresh cache in Manager (+ purge cache in Discover and Update)
clear Joomla + browser cache
 
I'm working on fresh install of joomla 2.5.9 and fabrik 3.0.6.3.

after all the steps:
Fabrik Administration Composant 3.0.7 ${createdate}
Fabrik Package Site Paquet 3.0.6.3 September 2012
The problem announce is now translated, but is still there.
 
yes, yesterday.
edit: i did it again, but nothing change.
Edit2: i tried the formulaire, no more error 500, i'll try a registration.
 
I confirm what Troester says: even setting "alter existing element types" on "Yes", the password element does not try to change the type from var(100) to TEXT.
What is the engine type for this table in the database: MyISAM or InnoDB?
What are the settings of your server (PHP, MySQL, Apache,...)?
 
Version de PHP : 5.4.4-10
Serveur web : Apache/2.4.3
Version du client de base de donn?es : libmysql - 5.5.28
Extension PHP : mysqli

my registration test worked with the varchar/TEXT conflict.

now i have a lot of work, thanks to you!
 
Status
Not open for further replies.
We are in need of some funding.
More details.

Thank you.

Members online

Back
Top