[Done r1694] Grouping fields list in template

ggppdk
Offline
Administrator

11 years 5 months ago #38367 by ggppdk

Replied by ggppdk on topic [Done r1694] Grouping fields list in template

Hello,

Menu item is
"submit menu item", it is not used while editing

and for editing it is less meaningful to set it ,

since each time the item is edited the user will get a FREE "refresh" of publication expiration time

-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star...

Please Log in or Create an account to join the conversation.

brandonking
Topic Author
Offline
Platinum Member

11 years 5 months ago #38369 by brandonking

Replied by brandonking on topic [Done r1694] Grouping fields list in template

since each time the item is edited the user will get a FREE "refresh" of publication expiration time

I have tested with item that has been auto Published Up and Down, but the item's publication expiration time didn't change even if author edit the item. Of course, author has edit own privilege though.

At the moment, if author edit item, "the item will be reviewed by admin" message appears.

Please Log in or Create an account to join the conversation.

ggppdk
Offline
Administrator

11 years 5 months ago #38371 by ggppdk

Replied by ggppdk on topic [Done r1694] Grouping fields list in template

Hello,
what do you mean change? why should they be changed , they are scheduled to specific dates

-- these will remain unchanged for ever,
unless a user with EDIT.STATE privilege edits the item and sets them to a new DATE value

Please Log in or Create an account to join the conversation.

brandonking
Topic Author
Offline
Platinum Member

11 years 5 months ago #38519 by brandonking

Replied by brandonking on topic [Done r1694] Grouping fields list in template

ggppdk wrote: Hello,
what do you mean change? why should they be changed , they are scheduled to specific dates

-- these will remain unchanged for ever,
unless a user with EDIT.STATE privilege edits the item and sets them to a new DATE value

Once un-publish date reached, item isn't available to public.
An this item should be unpublished in backend as well.
But still "published icon" displayed in backend even if another small icon shows as publication expired.
Or maybe this is normal?

[attachment=1:3nqdvnpr]screenshot17.jpg[/attachment:3nqdvnpr]

[attachment=0:3nqdvnpr]screenshot18.jpg[/attachment:3nqdvnpr]

And I have custom developed plug-in to display total item, and above item was counted as published.. Below is the sql query that I used..

Code:

$sql = 'SELECT COUNT(DISTINCT i.id) AS items_total,'."\n"
		 .'  t.name AS type_name, t.id AS type_id'."\n"
		 .' FROM #__content AS i'."\n"
		 .' JOIN #__flexicontent_items_ext AS ext'."\n"
		 .'   ON i.id=ext.item_id'."\n"
		 .' JOIN #__flexicontent_types AS t'."\n"
		 .'   ON t.id=ext.type_id'."\n"
		 .$join_cats
		 .' WHERE 1 AND i.state IN (1,-5) '
		 .$where_cats
		 .' GROUP BY t.id ';

Attachments:

Please Log in or Create an account to join the conversation.

ggppdk
Offline
Administrator

11 years 5 months ago #38521 by ggppdk

Replied by ggppdk on topic [Done r1694] Grouping fields list in template

Hello,
no no, this is not the meaning of publish_down Date

-- the publish down is not designed to change state of the item
(Nor in Joomla, neither in FLEXIcontent)
(there are extensions that can change state when publish_down is reached, we have some code for this implemented but we did not enable it because there powerful extensions for this, JUST AVOID using "In-progress: Published" State if you use these extensions)

-- An FC item/ Joomla article is consider published if:
1. is in a published state
2. current date is in range [publish_up, publish_down]

NOTE:
Your plugin code is wrong it must also check publish_up and down code, check code of joomla, FLEXIcontent and any other extension and you will see exactly 2 checks for publish_up and publish_down dates

-- Correct code is:

Code:

// Limit by publication state.
$where .= ' AND i.state IN (1, -5) ';

// Limit by publish up/down dates.
$db     = JFactory::getDBO();
$_now = 'UTC_TIMESTAMP()'; //$this->_db->Quote($now);
$nullDate	= $db->getNullDate();

$where .= ' AND ( i.publish_up = '.$this->_db->Quote($nullDate).' OR i.publish_up <= '.$_now.' ) ';
$where .= ' AND ( i.publish_down = '.$this->_db->Quote($nullDate).' OR i.publish_down >= '.$_now.' )';

Regards

Please Log in or Create an account to join the conversation.