fedora-infrastructure

#7842 Update/remove WordPress plugins on Fedora Community Blog
Closed: Will Not/Can Not fix by kevin. Opened by jflory7.

Closed: Will Not/Can Not fix
Reopen Issue

Summary

Update most WordPress plugins and remove some on Community Blog

Background

Some time in the last couple of weeks, some plugins stopped working on the Community Blog that were important to our workflow, like public preview URLs. I don't see an option to update them from the web UI, but comparing to my personal blog, they are out of date. Perhaps this is why they have broken.

Details

The following changes are requested:

  • UPDATE: Akismet Anti-Spam (4.1.1 => 4.1.2)
  • UPDATE: Code Prettify (1.3.4 => 1.4.2)
  • UPDATE: Featured Images in RSS w/ Size and Position (1.4.8 => 1.5.2)
  • UPDATE: Jetpack by WordPress.com (6.6.1 => 7.3.1)
  • UPDATE: OpenID (3.4.4 => 3.5.0)
  • UPDATE: Public Post Preview (2.7.0 => 2.8.0)
  • UPDATE: Varnish HTTP Purge (4.1.1 => 4.8.1)
  • UPDATE: Yoast SEO (8.4 => 11.2.1)
  • REMOVE: Edit Flow
  • REMOVE: Hello Dolly

These updates may also need to be applied to the Fedora Magazine installation too.

Outcome

  • Broken plugins important to our workflow hopefully start working again
  • Running updated and patched versions of plugins, some that were security patches

cc: @bcotton @pfrields

So, we can try and do this, but anyone with ssh access to the instance could also (which is @jflory7 @nb and @chrisroberts )

You can unpack the new plugins or remove plugins in /usr/share/wordpress/wp-content/plugins

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

@kevin Is there an SOP on how to do this? I have never administered this machine and I would be more comfortable doing it if I understood how it is managed today.

Also it's probably good to add @bcotton to the SSH access for the short-term, pending the research into migrating to WordPress.com for hosting.

@jflory7 note that Fedora Infra Cloud instances are fully managed by their VM owners.
So the people with admin access to the instance are responsible for managing and updating it, and you can add @bcotton yourself.

We do not have SOPs on managing wordpress, since we don't manage it, but I think that what Kevin said should get you started: download the new plugin archives and extract them in the indicated directory.

I did not realize I am recognized as an owner of the CommBlog infrastructure until now.

In October/November 2015, @decause worked with @chrisroberts, possibly others (to my knowledge) to set up the Community Blog but I was not involved with this. I volunteered to help but I didn't know I inherited ownership of the CommBlog infrastructure. Since I am stepping back from Fedora and I have passed up my rights as an editor to @bcotton, I should not be recognized as an owner of the CommBlog infrastructure.

Is there a policy in place for unmanned VMs in the Fedora Infra Cloud?

ok, we can add @bcotton here. @bcotton: Do you want to work on these upgrades?

There's no hard policy, but services/vm's we notice aren't active we retire... we will likely have a more formal and strict setup for the new community openshift setup.

Sure, I can take this

Is this now moot since things are moving to a new instance? If so, can we close this?

Or is there anything else we can do here?

@kevin yeah, I'd say we can close this. I'll re-open if it becomes relevant again.

Metadata Update from @kevin:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.