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

arkadiy, about route.php, thanks, when we had fixed for v1.5.6 (J1.5) we did not add an appropriate fix for v2.0 (J1.7+), will include a similar fix in next commit today

effrit, about item ordering we have a defect issue that is still open, will check it today if it is small/easy i will commit fix today

next days will test with J2.5 and try to close remaining defects issues too, some of the bugs that are now in v2.0 RC2a you will not see them in bug tracker because they are already fixed,

also by end of week will make a nightly build strictly for testing

Regards

Because I have to work with flexi and Joomla 2.5 I try to make some changes to add compatibility.
(for backend only)
-I add prefix value FlexiTable on each /tables/*.php
-search JTable::getinstance and replace every '' with 'FlexiTable'
-search getTable and replace every '' with 'FlexiTable'
search JRule and replace with JAccessRule

there are probably other changes do do but for the moment I have no more errors.... if it can help developpers

Hello,

I have a problem when testing the 1.7 r1057.
When a menu go to a unique item, if the item is in Draft or not published, the document is show to the guest.
So, in models/item.php, after "function &getItem" I add

$user = & JFactory::getUser();
if ((!$user->authorise('core.edit.state', 'com_flexicontent')) && (!$user->authorise('core.edit', 'com_flexicontent')))
$this->setState('filter.published', 1);

Because, when a guest access to an unpublished item , the filter.published is not set.

I think my hack is not good because in some plugin like page navigation, unpublished item are shown...

Thanks

mmm, the item should not be visible unless you are logged in frontend as administrator, you can see it without being logged?

UPDATE: i tested and opened a defect issue to fix

Regards

hi,

in category view (default layout) pagination is not responding to # per page. 10 items per page are displayed regardless the settings.

greetings

There are many bugs fixed since v2.0 RC2a r1057, this is one of them.

Thanks for reporting, regards

Also just now commited fix for triggering content plugins in category description, see here:
flexicontent.org/forum/index.php ... pic#p21737

Hello,

I just tried upgrading my site to 1.7 with Jupgrade. Once the data was all moved, I logged in and installed your flexicontent for 1.7 and then turned all of the plugins on and saved global config. I then went to items and went through the binding process. All of the items are there but the fields are all gone - like images. Is this a bug or did I do something wrong?

sb.artisanwebandprint.com I'll wait to hear from you before I revert to 1.5

Note, the menus are mixed up too. I tried to reconnect the Auction menu item to the category menu via the Flexicontent>Category menu item type and received this error: Save failed with the following error: JTableMenu: :move Failed - Cannot move the node to be a child of itself
Thanks,

Dawn

Upgrade from J1.5 to J1.7/J2.5 is possible but we have not done it yet, priority is to release final version for J1.5 and J1.7/J2.5, so we cannot help you in this now, if we were to start this now, i have no idea how much time it would consume, maybe little maybe a lot.

There are some minor issues, like different parameters for some fields, most notably minigallery.

What you describe is a more serious issue. You should never have to bind existing items again!!! I cannot imagine the ids of the items being changed but i cannot say more without testing.

We will test after final version of v1.5.6 and v2.0

Regards

Hmmmmm . . .

JUpgrade changes the Joomla article IDs.
So this is going to wreak havoc with the FC binding to the advanced data.

And JUgrade changes the section and category IDs.
So that will also obviously affect things.

These ID changes are also going to affect the menu items.
With the ID changes the FC links are all going to break.

JUgrade does have a plug-in system (not well documented) which may enable this migration to work.
But as you said, have to evaluate that later after the upcoming FLEXIcontent releases.

SP Upgrade maintains much more of the existing article and category IDs than JUpgrade does.
It is done by moving some of the new default IDs around to make room for the old IDs so they can stay the same.
They do this to help maintain existing incoming links.
With SP Upgrade it may be possible that the FC binding will not be broken because the article IDs have not changed.
Dunno.
Have to look into that . . .

This migration discussion really needs to be a whole new thread.

George,
I'll think about this a little more and start a new thread to discuss the migration process.
First thing to do is warn users not to do it right now.


.

Ken, thanks for this info,

closing remaining known bugs and finishing some almost completed features takes quite some time.

You are right, we need a new forum thread for upgrading, please start one, adding the info you included in your last POST.