SpencerLavery

Regardless, I was not impressed with his comment stating that he hoped WordPress developers don’t address the issue noted in that thread simply because a small group of users are passionate about it. He used the word stubborn, and implied our needs were less important than others’. Not appropriate behavior for a moderator in my opinion.

I called his comment “child-like” and my reply was edited by a moderator removing the entire sentence directed toward Moshu. I am unsure as to why, “child-like” is far from profanity and in that instance, rather apt.

It’s not a particularly big deal, I would just like an explanation for the double standards.

Otto42 you seem to be under the impression that your opinion is of more weight than other people’s, or even the general consensus. I disagree. I have conducted many usability tests with many candidates and these tests have shown that what I have stated above, is not the expected behavior.

A post belonging to a category should have the category in the URL all the while it belongs to only one category. It creates a logical folder-like structure.

My ideal outcome would be for WordPress to allow the proper use of %category% in the permalink, when I have made a conscious decision to use WordPress as a CMS, and set myself and other site users a rule to only place posts within one category. Multiple categories is an excellent function but mostly used for blogs. Poeple don’t always use WordPress as a blog, and that’s half of its appeal to me.

The post was however edited to remove my comment directed toward Moshu. This was my main issue.

Properly structured URLs should be hackable, for example:

https://domain.com/category-name/subcategory-name/post-title/page2
https://domain.com/category-name/subcategory-name/post-title
https://domain.com/category-name/subcategory-name
https://domain.com/category-name
https://domain.com/

It’s a simple matter of logic.

This is the way that most, if not all other CMS permalink structures behave.

It doesn’t necessarily help with SEO, but it does help massively with usability. With WordPress as it stands, if you remove post-title from the following URL, you hit a 404:

https://domain.com/category-name/post-title

This is not the expected behaviour, therefore it should change.

Relevant articles on the benefits of URL-hacking:

https://jerz.setonhill.edu/writing/e-text/url-hacking.htm
https://www.useit.com/alertbox/990321.html
https://blog.paramagnus.com/archive/2007/03/20/467.aspx
https://simonwillison.net/2003/Jul/30/newsSiteURLs/

It’s not a new concept by any stretch.

[Moderated: Post released from Askimet Spam Filter]

Should I take that as a no, then?

Show me a blog of yours with it working with both subcategories and pagination then.

I haven’t set it up at all. I took one look at his comments and saw people experiencing the same problems as I had with Top Level Categories and thought it a waste of my time. Admittedly this is laziness, but it is considered laziness, haha.

If you show me it working I’ll give it a go though.

Yeah apologies on my part also – I wasn’t best pleased at being accused of being naive, ignorant and burying my head in the sand.

But back to the discussion at hand:

I agree that security vulnerabilities need to be patched as soon as they’re made aware of – but I as the developer would rather know about these issues/upgrades BEFORE my clients do. Historically I’ve done that by checking the WordPress site often, and that is something I’m more than happy to do.

I don’t think that that is an unreasonable request at all.

Hacking the ‘open-source’ WordPress is all well and good until one month later I *need* to upgrade and re-do the hacks completely. As I’m sure you’re well aware, when it comes to managing 20+ installations, even remembering which hacks you’ve implemented on which blog is a task in itself.

Note: I should point out that the majority of these clients have no on-going maintenance contract with us, therefore keeping these installations up-to-date is a free, courtesy service that is increasingly eating more and more of my time. Where to draw the line with regard to support and ‘secure’ applications is very blurry in this case indeed.

Who is burying their head in the sand???

I’d like to see you try to keep over 30 blogs up to date and not get frustrated by the short lives of each release.

We predominantly use custom build CMSs where I work, and have over 100 deployed, most of which for years, and are yet to experience any ‘security’ problems. It is entirely possible to create safe and secure web applications, and if running WordPress is “vulnerable” to quote you, then I think it’s high time we all switched over.

I think the WordPress devs would have a fair amount to say about that claim of yours.

I’m not complaining about having to update anyway, I’m frustrated by my clients seeing a “your WordPress is out of date” note without any prior knowledge, features like that should be marked clearly on the upgrade page to give people like me time to prepare themselves for the barrage of 30 panic-stricken phonecalls.

I’m sorry but if you think having to go through a complete upgrade every single month is acceptable for a web app then you’re the one that is naive and ignorant, and have clearly never worked with a professional web application in your life. I accept the shortcomings of using a popular open-source app, but don’t tell me all apps are like this because they’re simply not (used Expression Engine lately? Mephisto? Light CMS?). You’re a fool for thinking so.

Thanks I’ll take a look ??

That suffers exactly the same problems as the Top Level Categories plugin, whereby pagination and subcategories stop working.

It’s not a solution, it’s a hack that breaks key functionality and looks exactly the same as the Top Level Categories plugin to me.

I’m of the opinion that every major release (such as 2.3) should already be safe and secure!!!

If a release isn’t ready to be stable for at least 6 months it should be beta tested for longer. WordPress are updating with security fixes more than bloody Windows these days. At least Windows has the courtesy to automate its process.

Keeping a single blog up to date is becoming a job in itself, but managing over 30 is just incredibly soul destroying. I’m not sure how many more ‘updates’ I can take.

You shouldn’t need a plugin for something as fundamental as this. WordPress needs to update less frequently and test their betas for longer, or it needs an automated behind the scenes update process.

I’m managing over 30 blogs and I thought it would be wise to upgrade them to 2.3 when it came out, only now I’m inundated with confused phonecalls from clients screaming “Help! My blog is out of date!” Explaining that upgrading is a chargeable service is becoming extremely tiresome, this needs to be disabled immediately and opt-in!

Is it possible to enable themes on a per-user basis?

I’m looking for a solution to ease the upgrade process of the 27 WordPress installations I manage, but each would need its own theme and to not have access to the others, is this possible?

Thank you! I’ll give that a go.