maximum allowed edit time

  • I was going through the demo and perhaps I missed it. But this is also a problem with the current blogging software I use from a different development. And before I migrate to Woltlab I really need this feature.


    I would like to set a maximum edit time for blog post and blog comments. I find when someone has an unlimited edit time, it is easily abused. It's not good if today their blog is about "X" and 3 months from now they edit their blog to add spam. Just as it is no good if they have 1,000 blog post and later decide to go on a mass delete spree.


    So if this is not a feature, I would like to suggest it (if it is and I've overlooked it, please let me know). This would be far to important to depend on an addon (if there is one).

  • I added that to our internal issue tracker as soon as i saw this thread ;)

    "A life is like a garden. Perfect moments can be had, but not preserved, except in memory. LLAP" — Leonard Nimoy

  • I recently just experienced this today. :(


    Someone had posted about 21 blog entries. And unfortunately, there was no edit time limit for the blogs, so they could edit the blog anytime they wish. In this case, 6 months later.


    What originally was cute cat photos, just got changed into spam links for gay porn. <X


    If there was a setting that would limit the window of opportunity for editing blogs, this would never have happen. :rolleyes:

  • MORE gay porn today. <X


    I'm sort of concerned that the rest of the innocent photos people shared in the past, will be edited into porn links. Found 4 accounts doing this and had to terminate them. Sort of worried how many other nasty things could be changed later.


    This is why you need to have a setting that restrictions the maximum edit time in blogs. For the same reason many people do not allow unlimited edit time on forum post.

  • I'm glad to see this planned.


    I converted someone's site to 4.0 (not 4.1) and they faced a similar issue. For now they've disabled their blogs and are waiting for 4.1

  • I hope it includes all comment areas ;) I guess it uses the same system so should do...

    God I hope so...


    I just switched to Woltlab Blogs 2.0.11 and you know anytime you switch platforms there is always that 1 troublemaker that suddenly comes out of the woodwork, announces how they think things suck, and try to get everyone to go to their new site... Ya... Having an edit time limit would have helped.


    The little guy was sneaky too. His original blog said how much he loved the new site. Then 2 days later edited to tell people to go else where. :rolleyes:

  • @Marcel Werk Sort of worried this is marked planned, but no word on when.


    I have Woltlab Blogs 2.0.11 and the unlimited edit time is a problem, given that I have a few troublemakers who re-join and post harmless things such as cat photos, but a month later change their post to either gay porn or spam.

  • Comments are delivered by WCF, and new WCF features will only be introduced with WCF 2.2.

    "A life is like a garden. Perfect moments can be had, but not preserved, except in memory. LLAP" — Leonard Nimoy

  • Comments are delivered by WCF, and new WCF features will only be introduced with WCF 2.2.

    One would hope blog replies would, being part of the blog app ... Would count as a whole for blog replies (comments) and would be outside of the framework.

  • Well, the great thing when you are using modular software is that is is, you know, modular.


    WoltLab has developed the comment function as part of the framework. This means they can use the comment function easiy in many places without the need to re-implement it every time. So you get comments in user profiles, in the file base, the blog and the gallery. And the beauty is, you don't need to create the comment system in each of these places again, but instead use the modular thing you have build for the framework. That is the whole reason why frameworks exist in the first place, and why they save time and money.


    It also means that the function works consistently in all those places. But it also means that you can not change it in one place without it affecting other places as well. If you want changes to the comments, make a suggestion for the framework, because that's where the comment function resides (you should make a new thread for each suggestion anyways, so even if you were to create it in the blog section, it would get moved to WCF).

    "A life is like a garden. Perfect moments can be had, but not preserved, except in memory. LLAP" — Leonard Nimoy

  • The edit time for comments on threads

    This counts as "posts" and not "comments" there is a big difference.


    Threads ands posts are part of the WBB application and not part of the WCF framework.


    The thing Marcel has implemented for WL Blog 2.1 is that the Blog Entries have a new "permission" max alloed edited time as you suggested.


    But this does NOT count for comments to it.