Hi,
It is all kind of a mess now.
I have tried to uninstall and reinstall and it all went terribly wrong...
It said it did uninstall all but one table..
However when I was trying to reinstall it failed and now it has files left every ware....

Is there a way to speak with you?

Amir

Don't worry,
it's easy to fix.

If you trust me, I can access to your Joomla backend and solve the problem. Many times I do this for users on this forum. In this case, send me an email with a temp account info. You can find my email in "Contattaci" menu item on the left.

Regards,
Luigi

I did send the email to Questo indirizzo e-mail è protetto dallo spam bot. Abilita Javascript per vederlo.

Hi Amir,
to be sure to remove completely components and plugins follow these istructions:

TAG META COMPONENT
Drop _tagmeta table
In administrator\components delete com_tagmeta folder
In administrator\language\en-GB delete en-GB.com_tagmeta.ini file
In administrator\language\it-IT delete it-IT.com_tagmeta.ini file

TAG META PLUGIN
In plugin\system delete tagmeta.php and tagmeta.xml files
In administrator\language\en-GB delete en-GB.plg_system_tagmeta.ini file
In administrator\language\it-IT delete it-IT.plg_system_tagmeta.ini file

REDJ COMPONENT
Drop _redj and _redj_pages tables
In administrator\components delete com_redj folder
In administrator\language\en-GB delete en-GB.com_redj.ini file
In administrator\language\it-IT delete it-IT.com_redj.ini file

REDJ PLUGIN
In plugin\system delete redj.php and redj.xml files
In administrator\language\en-GB delete en-GB.plg_system_redj file
In administrator\language\it-IT delete it-IT.plg_system_redj file

Hope this help.

Regards,
Luigi

Hi,
Sorry it took me some time to update but it is better never than ever...
I did manage to clear prev installation thanks for the the easy to follow instructions.
It did clear all earlier work as expected however, I still have the original problem.
I have created item and after saving it I can not access it because I am getting "currently being edited by another administrator" error.

What can I do next?

Amir

Hi Luigi,
I did manage to clear the prev installation, thanks for the easy instructions.
However I do still have the same issue with the "currently being edited by another administrator".

I am not sure if it is any help but I have similar issue with the ReDJ.
I was trying to deal with some 404 errors and I am getting The list www.???????.com/, is currently being edited by another administrator (the ????? replaces the real domain). And the redirect does not take place I will create another post in the right place.

Any advice?

Amir

Hi Amir,
this issue were caused by a wrong table structure, but should be corrected in version 1.2.

So, could you please, send me a dump of Tag Meta table?

Thanks,
Luigi

I figured out the cause of the problem and there is a simple fix for it.

Problem: Some members cannot edit and TagMeta entries. Error: "Currently edited by another administrator".


Cause:

-Table 'jos_tagmeta'

-Field 'check_out'

The 'checked_out' field (as of TagMeta v1.2) has TYPE set to "tinyint()".


Solution: Change field type for 'checked_out' in table 'jos_tagmeta' to "int()".

Why? http://dev.mysql.com/doc/refman/4.1/en/numeric-types.htmlSee http://dev.mysql.com/doc/refman/4.1/en/numeric-types.html.

Type Bytes Minimum Value Maximum Value
(Signed/Unsigned) (Signed/Unsigned)
TINYINT 1 -128 127
0 255
SMALLINT 2 -32768 32767
0 65535
MEDIUMINT 3 -8388608 8388607
0 16777215
INT 4 -2147483648 2147483647
0 4294967295
BIGINT 8 -9223372036854775808 9223372036854775807
0 18446744073709551615

Therefore, members with ID's higher than 127 will be assigned a value of 127 in the 'check_out' table. This creates an authentication conflict when you go to edit something (due in part to how the php function is coded) which locks the field for editing then fails because the users ID does not match the check_out ID in the jos_tagmeta table.

With the TYPE changed from "tinyint()" to "int()", this issue is resolved.

Hi,
you are absolutely right, infact this issue was fixed into 1.3 version (not released yet).

Only some users has received the "alpha" version that include this fix. Anyway, with respect the first table version, these are the change needed:



Thanks again for post and support,
Luigi