I’ve been working on a site which currently has hundreds – and will have thousands – of files to be stored somewhere. But the current media management is completely unsuited to this, so we have had to store them off-site.
As I understand, WP 4.9 didn’t have any Gutenberg code, but the latest security release is 4.9.16, released October 29, 2020. The latest CP is older.
So, an usual user will presume, that the latest WP 4.9 bugfixes is not ported. We need a newer release or the announcement, that these security flaws is not affecting CP.
We need a newer security release or the annoucement that these 4.9 vulnerabilities not affecting CP.
As said in Slack: this has come up a few times, and I haven’t seen agreement on what to switch to, or a workable plan that will actually get us through the migration without losing too many active users. I also don’t agree that Slack is not “suited to a community” - Slack, the forums and GitHub all serve our purposes well but slightly differently, with some overlap between them. In summary, there are much higher priorities for us, and I think this is not too likely to happen in 2021.
I agree with this. Part of the reasoning behind the petitions system was that developers who know their way around the internals of WP/CP would arrive to work on the things they are interested in. That hasn’t happened at anywhere close to the scale required in order for such a system to be successful, and so far there are many more ideas than there are people to work on them.
I think it’s reasonable to argue that the petitions have already served their purpose: help us set the direction for ClassicPress v2 (and beyond, realistically there is too much in just our existing roadmap to pack into only one new major version). This would mean that we can keep the existing petitions available as a read-only archive, and use other communication channels (GitHub, forums) for suggesting changes in the future. This would streamline things a bit for our users and also saves us the work of migrating petitions over here.
However I think it’s a good idea to be careful with any such change: we want to keep it very clear and obvious that we are listening to our community. The first thing the ClassicPress community has wanted is a stable version that isn’t going to spring new changes on them, and that’s what we’ve provided.
We are not aware of any directly exploitable issues that were fixed in WP 4.9.16. This was a security hardening release and we do not recommend making assumptions about security without understanding the actual issues at a detailed level. Still, we’ll get these changes released as soon as possible.
Please, make this announcement as a separate forum post, or, better - as a separate blog post. Because of what you know is very different from what non-technical user assumes.
Sorry for the repeating this over and over, but we should provide not only superior to the WP security, but also communicate it to the existing/potential users. (Yes, I am from the marketing world).
Still not understanding why they can’t just be plugins that you download and install in the usual way. If they are “rarely used” then why bother to ship them with core files and offer them up as an option in the installation process? If you must do this, wouldn’t it would make more sense to offer some that are “commonly used”.
Anyway, to summarise my initial point, I think the first 2021 goal should be a major rethink of where this is all going, taking into account the obvious fact that we have very few people who actually roll their sleeves up and contribute.
- Core plugins need to all be shipped with ClassicPress and enabled by default for the first few releases after this change, otherwise a bunch of sites will break.
- Core plugins will likely need to be loaded in a different way than other plugins.
- Core plugins should have a special status in the directory and in the users’ minds, because they were once part of the core code itself rather than plugins written by other authors.
Thanks James. That makes it much clearer.
To get more users to use ClassicPress. I have written a series of blog posts that didn’t see the light of the day, and one issue that is stopping my track each time is the lack of ClassicPress specific theme. It’s kinda not good for new users to use WP themes, and I guess you know why. New users should be presented usable CP theme right off the box.
@1stepforward what is your definition of a modern theme? what do you want extensible? and can you open a CP research repo for that?
3 posts were split to a new topic: Theme One Development
One thing that’s important to discuss, that I haven’t seen anyone mention, is marketing goals for 2021.
Biggest issue I see on Twitter, for example, is awareness. People not knowing about ClassicPress at all. And when I mention it, they are eager to try it.
Since we’re a non-profit, one goal I would like to see attempted is applying for Google grant. $10,000/mo would make a nice ad campaign to increase awareness. https://www.google.com/grants/
8 posts were merged into an existing topic: Google ad credits for non-profits
Discussion about Google ad credits moved to its own thread: Google ad credits for non-profits
Viktor, I think that’s a great idea and I’d like to see some marketing goals for 2021 as well. Based on the lack of response the last few times I’ve called for a meeting, there seems to be very little interest from the community in participating in creating and executing those goals. I do plan to ask for another meeting in January 2021 and hope you and others will respond, attend, and participate in marketing ClassicPress in 2021.