Hi allkindsofreviews,

If you are using B2evolution 2.4.5 it's easy, but you'll have to take a few steps:
1) in Dashboard -> Global settings -> Post types add a new element called Sticky (or whatever name) It will have an ID of 5001

http://www.blog.hemminga.net/B2evoforum/Sticky-1.png

2) Open /blogs/index.php and add one line just before the end so the end looks like this:

// Stickies go first
$orderby = 'ptyp_ID datemodified'; 

// That's it, now let b2evolution do the rest! :)
require $inc_path.'_blog_main.inc.php';

?>

The line $orderby is the one that is altered.

Now when you write or edit a message you have an extra type (Sticky) for posts that will stay on top.

http://www.blog.hemminga.net/B2evoforum/Sticky-2.png

Note: I used datemodified as second sort order argument. You may want datecreated there.

Good luck

I wrote a HOWTO in the FAQ section based on this answer, see http://forums.b2evolution.net/viewtopic.php?t=17036

Thank you so very much!! :)

I tried this and it didn't work. I know you mentioned datecreate. How do you do that?

Simply replace datemodified, in the code Afwas posted above, with datecreate

I just give up none of this worked. When I inserted Datecreate it messed up the blog so I had to put it back to date modified.

Hi there.

This is a feature I'd like to have. Has anyone gotten it to work properly (before I try it)? :?:

Thanks.

This works.
If it doesn't work check if you're using stubfiles (Blog settings -> URLs). In v 2.4.5 the stubs are most likely called blog1.php through blog9.php. In that case you do not alter the index.php file but the stub file instead.

Good luck

I tried this and got the following error message after clicking on a post (so the post opens in full):

"WARNING: unhandled sorting: ptyp_IDWARNING: unhandled sorting: ptyp_ID".

I have four blogs and each one is fine until you view an individual post. I assume it's to do with a search string, but why would it cause an error when it works on the previous page?

Incidentally I also tried changing 'datemodified' to 'datecreated' but that really fouled the system.

UPDATE:- found a post which sorts this problem out so thought it would be helpful to put a pointer here for it: http://forums.b2evolution.net/viewtopic.php?t=15184

I got the sticky to install and work just fine - except when I no longer want it to be a sticky (I edit the post and change the post type from sticky to post) - it stays at the top of the blog. Thoughts? It's like it considers it a new post - even though the date is still the original post date of 11/4.

I have since written more posts, so now the once-sticky entry has moved down the page, but it's still out of order date wise.

Anyone?

Not life or death, just annoying. :)

I can be oh so simple and not need 2.4.5

I used this code in place of the one above in order to get my sticky to show up, and in order to also have my blog be in chronological order even when the sticky is removed.

// Stickies go first
$orderby = 'ptyp_ID datestart';

Hello.

FYI -

Also, take a look at this thread:

http://forums.b2evolution.net/viewtopic.php?t=17780

OT: blogmeister there was no need to tack a "look at this post" to everything related. Good find & potentially good fix for those into using the post type hack, but ... pointing everything to it doesn't really add value.

I appreciate your sentiment, EdB and agree in some cases but for those that asked for help or for just being proactive so that new users don't experience certain problems, it is sometimes easier to refer to a thread than to repeat the answer in its entirety.

Hello.

I just ran across this situation:

I have a post I want to keep in the #1 position in the sticky post listing, but because the new sticky post was created later and is then the most recent sticky post, it of course wants to take over that #1 position.

Any ideas, without altering a post's date, to have like a 2-tiered sticky post area? 1st tier for say, the #1 and #2 positions that could be more permanent postings and the 2nd tier would begin date-ordered sticky posts? :?:

Thanks in advance.

Afwas wrote:

This works.
If it doesn't work check if you're using stubfiles (Blog settings -> URLs). In v 2.4.5 the stubs are most likely called blog1.php through blog9.php. In that case you do not alter the index.php file but the stub file instead.

I am using stub files. My question is, do I have to modify each of the stub files (blog1.php through blog9.php) to get the stickies to work? AND, do I just add the "stickies" code from above, or do I need to add something else in addition...AND where do I add it?

Thanks in advance!

Hi Afwas. Refering to your FAQ http://forums.b2evolution.net/viewtopic.php?t=17036

In 2.4.6 are you saying that only the file [/inc/items/model/_itemlist.class.php] needs the extra case and there is no need to add type 5001:Sticky, or do both have to be done.

I've done both and nought happens. I noticed that 3000 was also a sticky so I went to the database and renamed it Reserved.

Thanks

By the way I have stubs and put the code in there and the index.php

SORTED: Thanks Afwas. I have the 5001:Sticky and modified the blush.php which is the 'real' stub file.

Thanks again

Hi delweldj

Hope you got it sorted by now its been a few weeks since your post. As I understand from earlier post, above, you enter the code before the last line of the stub files you mentioned, for each blog you want stickies to work for.
i.e before this:

// That's it, now let b2evolution do the rest! :)
require $inc_path.'_blog_main.inc.php'; 

Sadly I haven't yet got it to work yet

SORTED: See next post

Update: OK 'm getting there slowly.
Given that I modified the blog2.php, if I use blog2.php in the URL it works fine, but I'm now checking the issue with the named blog as blog2 directs to a folder [blush] which has its own blush.php and index.php which are the actual final parts of the url, rather than blog2.php

Final Update: Ok its sorted. had a blush.php file in the root folder which is the 'real' user friendly stub file. Modifying that got it working.

Thanks all