Closed steinmb closed 6 years ago
I saw it, but in practice, promoted to FP doesn't do nothing, right?
It will if we decide to use it. Example would be functionality discussed in #47. In other words we should never use it. This issue will try to mitigate this by removing permissions to this until we need it though we need to write special permission for this. The current permission scope is to wide.
Oh I get you, now I should go thru each of those 58 records and undo the promote to FP, right? And then we should also revoke the permissions, that is, only admins and editors can promote to front.
I think the majority was platforms and done by students in 207 last year, so it was an error. Others, such as https://elmcip.net/story/335-scholars-and-artists-submitted-proposals-elo2015 was done by me, since I think the only way i can create news (story content type) to pop-up in the news box in the homepage, is by creating a "story" and then promote them to FP. Correct me if im wrong.
Uff... 58 records. Cleaned them all. Now... everything living here https://elmcip.net/node are stories, meaning, records that (can't see where to find the nodes of which) pop-up in the NEWS box in the homepage
Thank you! Confirm that you got them all:
SELECT nid, title, type FROM node WHERE promote = 1 AND type != 'story';
Empty set (0.00 sec)
I think we can leave the story nodes as they are. They are not a part of the KB anyway. If they cause problem will I address them with SQL magic.
Good! But we should still address the permissions issue then.
One down.
commit 9e54051251cbf65921deb5b010800e0a2c251cd0 Author: Stein Magne Bjorklund steinmb@smbjorklund.com Date: Tue Sep 12 11:30:33 2017 +0200
Issue 269 - Remove /node and change news path to /news
Drupal comes with a default front page example.com/node. ELMCIP
uses another front page. ELMCIP also uses a view that pulls out
the nodes that is "promoted" to front page (views_recent_posts)
that create a short list on the front page + exposes all story
types, promoted or not.
This remove /node and changes news to /news to prepare us to remove
the block from front page and replace it with a menu link.
@AlvaroSeica this is the last task in this issue. Remove promote and sticky to all add or edit nodes except for Story
.
Note: To make sure they cannot be turned on by going to /admin/content
, administrative editor are allowed. I had to remove: demote, promote, sticky and unsticky. Here I had to remove it for all content types. These are batch options in a single list. No other way. This can completely removed in the future if we end up not liking this bit of the change.
ommit 935b41b86a92e9d627b0b2b733ed128eb271ef38 Author: Stein Magne Bjorklund steinmb@smbjorklund.com Date: Tue Sep 12 13:08:08 2017 +0200
Issue 269 Remove promote and sticky from all except story
Confuse some users with the power of to promote articles and we should
also make sure we do not populate nodes with properties we should not
have.
Also remove this option from the content overview page for the users
to access it.
Is there a reason this issue is open?
Checking..... No, I fixed it back in sept. Good catch.
Someone with permission have tagged a set of nodes as published to front page. Not sure if this is in on purpose. As far as I know do we not use this node tag in any of the content listings.
Suggested fix
How to test
promote
andsticky
option on both create new and edit existing./admin/content
should not have the option to demote, promote, sticky and unsticky.Content overview page - Before change
Content overview page - After change
Nodes updated