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

This release is not compatible with Joomla 2.5 beta because in JTable model is different.
Now if you do not specify a table prefix for your model it adds always 'Table'.

In flexicontent prefix was '' and now all JTable instances have to be changed.

it should be great to correct Jtable calls in Flexicontent 2 because now lot of people will begin to test and work with Joomla 2.5 as beta 2 will soon be released

Yes, this is our purpose to support J2.5 ..., see home page of the site, we will test very soon for changes needed for J2.5

FLEXIContent - 2.0 - preRC3 r1100 the transition from the home page on the link in the module
Solution:

hi!
it was reporting in other thread, but still i cant ordering my items.
Seems that parameter "Primary Order" (in categories properties "Parameters : Layout common") dont change anything.
i just want set order of items in category in according to "order" column.

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