Maybe this is just a glitch, but the options to acess one's blog, create a blog entry, or read an older blog entry have disappeared.
Is something wrong?
Anonymous
User login
Please support the defense of Ukraine.
Direct or via Unclutter App
Active forum topics
Recent content
Navigation
No Ads.
No Trackers.
No Social Media.
All Content Locally Hosted.
Built on Free Software.
We have complied with zero government requests for information.
Seems I can access (to read) other's blogs, but I cannot access to read my own blog entres or create new ones.
Am I being punished, or hacked, or is there something else?
Mine's not there either, so I'm sure t'aint pers'nal and Drupal has indigestion.
Go to my latest blog entry and then click on the link to DDTM' blogs? Can you see all of my entries? When I do this for Reverend Darkness, I can see all of his, when I try it for myself, I get nothing but an "Access Denied" page.
I can see them.
Try it now please.
-BDub
It shows up again in COntent Creation. The Ubuntu Beige G3 thread I started ws supposed to be a blog entry, but they weren't working this morning...
I just tried it and am not expereinceing the described problem.
Thanks!
(What happened?)
An admin changed a setting to restrict users ability to edit their own blogs, given the recent couple of controversial blog threads which users have taken it upon themselves to delete. They did not realize that this would cause the user to not be able to view their own blog.
As soon as I have a moment, I'll be changing the code to remove ability to delete blogs completely from the system for users. Most likely, I'll leave it so the user will simply 'unpublish' the blog, so that they can remove it from sight but not from the database permenantly.
-BDub
This makes sense, but why remove the ability to delete a blog?
If I want to clean up my blog and remove certain entries, can I not have that ability?
Why not simply write the deleted blog to an archival database upon execution of the delete command? This would allow the user to clean up their blog if they feel the need, but would permit the site to maintain a historical record of entries should need be to reference such in the future.
That's essentially what I mean by 'unpublish'. It's still in the database, admins can still get at it, but for all intents and purposes it's unavailable to the general userbase.
...so does that mean I can no longer see it myself?
Every now and then, I may want to go and clean up (get rid of) blog entries that I no longer want. Will I still be able to get rid of these from my view?
And what is the use case for keeping these deleted blog entries (just curious)? Is it somehow tied to some USA PATRIOT Act issue? Or does the deletion of the entry (and subsequent responses) cause performance issues in the database (thus the choice to make it unseen vice non existing)?
I'll have to check out the user viewing question. I'm unsure, however it's fixable if the user can still see them.
Personally, I'm Canadian and couldn't care less about US law (Yes, the server is in the States, yes the owner is in the States, yes the domain is registered in the States, so yes we might care, however I don't believe it has a bearing on this.) Also, the database is not negatively affected by this, though the search function might have a quick bit of trouble with it if it's already indexed that entry.
It's mostly so that we can check up on something that's happening even if the user has removed the blog. An example might be if a user made inappropriate statements against another user. In deciding if the user should serve a ban, it would be useful to go back and look at the actual conversation, rather than having to hear two biased accounts.
Seems to me that you'd just be creating unnecessary work for yourselves. If a user were to make comments that would warrant a suspension or ban, said user would still have the ability to "edit" the offending comments out before an admin received wind of them.
It would seem to me, that to effectively maintain a record of what has been said in a forum or blog, it would become necessary to deny users the ability to edit comments. While the ability to "unpublish" threads might provide a quasi-deletion feature for blog creators, the edit features offered by Applefritter allows users to pretty much defeat the purpose of "maintaining a record".
Just my two cents...
Regards,
Willy
...once a post has been replied to, you loose the ability to edit your own remarks. If no one has replied, you retain the ability to edit your remarks. All too often, I will post, and two seconds later, edit to correct a bad spelling, or a url that is not displaying as I though it would.
I say leave the edit function alone.
Is this true for blog entries as well? I distinctly remember editing out my posts in the 419 blog, before finally just deleting the whole thread.
Remember seeing this throughout the 419 blog thread: This message deleted by Managed Resistance
Regards,
Willy
...you are right, I have the ability to modify post in my own blog, even if someone has already replied to it.
PS: quit clicking "quote" and click "reply" instead.
I kind of like using quotes in my responses; it adds context. Do you find that it is easier to follow a message thread when people do not use quotations to add context?
Regards,
Willy
...I have my settings such that the posts are in a tree-branch display and can visually see what was responded to by who. It is just that repeating the whole previous post can be 'needlessly redundant' at times, especially when fewer than five people are talking about the same thing vice some of the hotter topics which have nad several sub-conversations stuck in the same thread branch (when, yes, it is almost a necessity to quote for clarity).
But usually I am good about figuring out who is talking about what to who.
...that that did not involve at least one good b0n9 #!t.
I would pay top dollar to see "Henry Kissinger vs. The Daleks".
Especially if Ben Stein played Kissinger.
As usual, my painstakingly raytraced lightcycles get no love.
Just kidding.
I'm all for the unpublishing thing. I have an... archiving obsession. I go out of my head when I can't find something that was once existant. I also know the value of hidden archives; as matter of fact, I would like to find a system that has an editing history, like a wiki.