@GigaBob

Well done, you found more b2evo 3.x flaws ;)
Althought some of them might be already fixed in [url=http://test.b2evo.net/HEAD/blogs/admin.php?login=admin&pwd=demopass]DEMO[/url]. Can you please check if they still exist and report back, if they are I'll move the post to the "bugs" forum.

thanks

1) ... not tested, but do your users have perms to post "published" posts in the blog?

2) Yeah, seen that, hate it ... deleted the plugin ;)

3) I rarely use the Fm so I can't help there

4) you get a similar error of you click an "info page" link ;)

5) Might be worth checking $params['content_mode'] for that page

The good news is .. there's still time to fix some of those before an RC1 :D

¥

Ok, DEMO'ed:

1) Still applies in demo.

2) Cant disable TinyMCE in user profile on Demo blog so cant test this.

3) Yes, also applies to Demo.

4 ) Yes, applies to Demo only this time clicking the link in "post by post" archives gave the below error rather than "nothing to display".

( ! ) Fatal error: Call to a member function get_metadesc() on a non-object in /var/www/vhosts/web7/web/HEAD/blogs/inc/skins/_skin.funcs.php on line 581
Call Stack
# Time Memory Function Location
1 0.0015 51588 {main}( ) ../blog1.php:0
2 0.0380 784012 require( '/var/www/vhosts/web7/web/HEAD/blogs/inc/_blog_main.inc.php' ) ../blog1.php:43
3 0.2349 7277396 require( '/var/www/vhosts/web7/web/HEAD/blogs/skins/evopress/single.main.php' ) ../_blog_main.inc.php:545
4 0.2732 9217000 skin_include( ) ../single.main.php:35
5 0.2745 9237680 require( '/var/www/vhosts/web7/web/HEAD/blogs/skins/_html_header.inc.php' ) ../_skin.funcs.php:468
6 0.2753 9250144 skin_description_tag( ) ../_html_header.inc.php:34

5) Demo has the shortened posts but does include pictures (at reduced size). I'm pretty sure this is just a new feature they've added? Or are other 3.2's not doing this? Still the issue of my blog not disaplying the pictures in these shortened posts which the Demo does do.

And thanks Yabba. Yes, users have permission to post public blogs. Will have a look at $params['content_mode']. Though not entirely sure where you mean I should be looking.

GigaBob wrote:

1 ) When you select "protected" for a post, hitting PUBLISH NOW when its ready will PUBLISH it available to the public. You must simply click "save" for it to go live as a Protected post. Not remembering is going to cause bloggers problems on one of my blogs.

Well, the button is named "PUBLISH NOW" and it just does what it says. I agree this behaviour could be confusing for newbies, though.

GigaBob wrote:

2 ) Disabling TinyMCE editer in user profile doesnt turn off the WYSIWYG editor button under the post area. If you click on WYSIWYG editor TinyMCE turns itself back on. Personally, Im happy to just stay away from the WSYIWG button but I have bloggers who are computer / internet / blogging novices and expecting them to understand this will get messy. Means I'm going to have to uninstall it which also means it is no longer availabe to bloggers who CAN get TinyMCE to work for them (I cant, its terrible).

I would think of the "Use TinyMCE" option in the user profile as a default setting. If you turn it off, TinyMCE is not displayed by default but you still have the possibility to enable it temporarily for just one post. Well, if you disable TinyMCE you probably do not want to use it spontaneously, but if we would remove the "WYSIWYG" button, I fear other users could complain.

GigaBob wrote:

3 ) Insert image only works in HTML editor screen (which will also be confusing to novices and another reason to uninstall TinyMCE). Not a major, just thought I'd throw it in.

This could be a bug, but to be honest, I neither use the TinyMCE nor I am interested in it, so I cannot help here.

GigaBob wrote:

4 ) Make post "Sidebar Link". The link / post doesnt show on the blog as a post (which is good) but does include itself in your sidebar "Archives" list if you have it set to "post by post". Cicking it takes you to a "Sorry, there is nothing to display" page. Not a good look.

This certainly sounds like a bug. I will look at it.
//edit: Fixed!

GigaBob wrote:

5 ) Searches result pages, Archives for: XXXX pages etc arent showing full posts. They are only showing the first few lines of the post without including pictures. Ive been expecting to find a setting somewhere for this but none yet?

There is a setting. A german user [url=http://forums.b2evolution.net/viewtopic.php?p=92090#92090]had the same problem[/url] with tag pages; you can change this behaviour by changing the "Post contents" setting in the appropriate section(s) on the Blog settings -> SEO screen.

Thanks TBlue.

I think that the Publish thing is a problem. A Protected or Private post is essentially still a "Published" post. It is simply published for viewing by particular people.

Point 5). Yes, that did it! Thank you. Have changed all available SEO settings to "Stopping at < more >" .

Regarding the Publish Now button:

Well, as I said above, technically it does what it says - it sets the post status to Published. I agree it may be confusing if you consider a protected post to be published in the sense that it is visible for a restricted group of people (I do not think a private post is to be considered "published", though - only the user who created it can see it!).

Well, what can be done to reduce the "confusion level"? Maybe a prompt like "This post is protected, are you sure you want to publish it?" when clicking the Publish Now button?

Tblue wrote:

Regarding the Publish Now button:
Well, what can be done to reduce the "confusion level"? Maybe a prompt like "This post is protected, are you sure you want to publish it?" when clicking the Publish Now button?

Yes, would be great and all it needs I'm sure. Maybe add - You must click "Save" instead of Publish for Protected / Private posts. - or similiar?

OK, I implemented this feature. It only asks for confirmation if the post status has been set to "protected", though.

You can (soon) try it on the [url=http://test.b2evo.net/HEAD/blogs/admin.php?login=admin&pwd=demopass]test server[/url].

For what it's worth, the edit forms only display the "Publish NOW"
button for status == draft only; not when editing a post that is
"protected" or "private" already.
At least this appears to be inconsistent to when the "Publish NOW"
button appears in the item lists.

For reference, I've just added this change to my branch/whissip (r6220).

(from an older email by myself)

blueyed wrote:

For what it's worth, the edit forms only display the "Publish NOW"
button for status == draft only; not when editing a post that is
"protected" or "private" already.
At least this appears to be inconsistent to when the "Publish NOW"
button appears in the item lists.

Then maybe the item lists only should display the "Publish NOW" button if status == 'draft'?