pkBlog - a simple MODx blog v.1.4.2 (12 Oct 09)

Hello,

Thank you for taking time to respond.

De-publication: Please do implement something easy and reliable for this in PubKit. A progress report would be nice to see whenever you’re up to it.

We are using pkBlog as a *news* posting format rather than as a blog per se, so it would be good to have this. Also, the same format can be used for posting ephemeral announcements, so a publication expiry method would be very good to have. I’m also looking at using it as a ’job postings’ tool, with one post per position, un-publishing would permit re-using job listings.

In my case it’s more important that it is un-published rather than hidden.

Thank you, and I hope you can soon release PubKit.

Thank you, Tom

What causes this error in the post-edit page??

« MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« PHP Parse Error »

PHP error debug
Error: strftime() expects parameter 2 to be long, string given
Error type/ Nr.: Warning - 2
File: C:\xampp\htdocs\dev_modx\manager\includes\document.parser.class.inc.php(770) : eval()’d code
Line: 16

Thank you, Tom

A future development suggestion: you have prefixes pw and pk -- please use only one!!
It’s very confusing to keep track of different prefixes in this quite complicated addon.
Thank you, Tom

The thread at http://modxcms.com/forums/index.php/topic,35089.0.html may throw some light on the strftime() problem (if it’s the wrong widget in your date TV, or due to a server offset time).

Re naming conventions, I try to keep it so that things that don’t change from one application of pkBlog to another keep the pk prefix, and site-specific chunks etc. have something typical of the site (pw for Pogwatch, in this case). There are probably inconsistencies, though - I’ll try to iron them out in future examples!
KP

Quote from: kp52 at Feb 25, 2010, 02:14 PM

The thread at http://modxcms.com/forums/index.php/topic,35089.0.html may throw some light on the strftime() problem (if it’s the wrong widget in your date TV, or due to a server offset time).

The xampp server is in a VM on my PC...so it’s hard to think it’s time offset, since server time offset = 0.
Checking the two date TVs, they are correctly done according to your instructions.
However when the site goes live I may need server time offset...

I saw this in one of your posts: [+myDate:date=`%A, %b %e, %Y`+] -- would this work anywhere in pkBlog??

Also double-checked the timezone in php.ini -- it is correct.

Also the forum thread you mention refers to strftime thinking about receiving an array instead of a long. My error is strftime thinking about receiving a string instead of a long.

Quote from: kp52 at Feb 25, 2010, 02:14 PM

Re naming conventions, I try to keep it so that things that don’t change from one application of pkBlog to another keep the pk prefix, and site-specific chunks etc. have something typical of the site (pw for Pogwatch, in this case). There are probably inconsistencies, though - I’ll try to iron them out in future examples!

The only inconsistency I saw was pw’s where one might expect pk’s.
It is not immediately obvious to anyone that pw means pogwatch.
Should be easy to fix, good luck!!

Please post an update about pkBlog/pubKit development/progress to the forum soon.

Thank you, Tom

I hope you continue development on this project and that you find time to document how things fit together, particularly since this requires so many files (aka chunks, templates, etc.), which make it more challenging to style it for one’s particular website.

I had to give up on this because it’s not suitably clear how one gets the post-edit to appear from post-manage minus date issues without filling a date into the post-edit template per se.

I will check back someday to see if a newer, more fully documented version has been released.

I wanted to like this addon because it has the ability to un-publish something, yet it seems to require too many files/chunks/etc. that are closely interwined and not sufficiently explained IMNSHO how they work together.

If I understood better how things fit together in this addon, I could easily write good documentation.

Perhaps I will try again in a few days, weeks, or months.

Thank you, Tom

It was very hard to build this mod in for me but it’s allready running smooth and I’m still tweaking it to my preferences ^^

Great job !

I really like this Front End editor. I’m just running into a few issues here. When I create a new blog its not using the correct template for it, although I did specify it in the call. I worked through this thread and it seems multiple people have that problem. I found no solution though.



Second of all, is it possible to create a new blog item and at the same time restrict the access to it so that only siteadmins can view it? Or does this require additional scripting?

&template=`Texemus Global` ... &template=`pwBlogPost`

Have you tried it with just one template parameter?

On restricting viewing, can you give more detail on what you want to achieve? If you want most posts to be generally available, but keep some on the same set for admin eyes only, you could do that by leaving them in the "preview" state - just go to another page when the item has been screened as a preview, leaving it unpublished and marked as a "draft" in the management list. You could make page with a Ditto call listing unpublished items with the preview flag set to bring them together. Solutions that look more obvious to the user may well require some more code.
KP

Hi Keith,

thanks for this great snippet. Just installed it on my site. Now I need to custom it a little bit, hope you can point me in the right direction. How can I make it so that each blog-entry can only be edited/deleted by the webuser (and the admin) who created it?
I will edit the php files, not problem, just need to know if it is possible and/or if there is a solution/workaround for it available.

Greets
Dirk