FLEXIContent - v2.0.0 - final for J2.5 released (r1648)

sinjinn, i install latest beta on comletly new installation of Joomla without any error.
i think its most suitable method for testing beta versions

Goto to phpmyadmin
find table jos_menu and delete the record of the COM_FLEXICONTENT


This should fix the error then:
Reinstall flexicontent v2.0 beta

Hello,

to notify, i use flexicontent Beta 2.0 r907

with field type "flexicontent-text" doesn't keep value in article.

the value is in table and appear in front end but after save article, if you open this the field is empty. Just not display !

swall

Thank you very much. The removal of the record in the _menu table solved it. My apologies. I'm sure it was from my attempt to install the old version first. Thank you for a great product. I'm eager to try it out now.

Arkadiy wrote: 1.
ru-RU.plg_flexicontent_fields_extendedweblink.ini
ru-RU.plg_flexicontent_fields_date.ini
saved in ANSI instead of UTF-8 no BOM.
2. Undefined constant FLEXI_FIELD_THUMB_IN_ITEM, FLEXI_FIELD_THUMB_IN_CAT, FLEXI_FIELD_LINKTO_URL
FLEXI_FIELD_URL_TARGET, and ..._DESC
and FLEXI_FIELD_SAME_FRM_WIN_TAB, FLEXI_FIELD_NEW_WIN_TAB, FLEXI_FIELD_MODAL_POPUP_WIN
on image plugin
3. Move Up, Move Down, Save Order not work on fields list.
4. No duplicate templates.

Fixed will post new beta today

effrit wrote: still versioning error!
by default versioning content is active, but if i edit item from frontend i cant see my last changes: i press "save" and my content replace with one i create on submission (and new version i can see only on backend). this logic is strange for me - at least i must can open for editing my last changes even if other users see last approval version.

Yes this is confusing to the user, you are right this is not the "wanted" behavior.
If i remember correctly this was changed by enjoyman at v1.5.6. I mean v1.5.6 will show load for editing the last unapproved version. Will look into it.

effrit wrote: and if i disable versioning i cant changes my items from frontend. i think the error produced by wrong index of current version which still link to unapproval content, instead of last approval

Yes, code is broken without versioning enabled, and needs to be fixed.