Differences

This shows you the differences between two versions of the page.

--- berkeleylug:wordpress [2024-09-09T08:55:09+0000] – created (at least initial starting version) michael_paoli_admin
+++ berkeleylug:wordpress [2024-09-10T23:53:02+0000] (current) – fix transposition michael_paoli_admin
@@ Line 1: / Line 1: @@
-====== Manually Updating Plugins ======
+====== Updating Plugins ======
 Debian (at least >= 12)
   - see: [[https://berkeleylug.com/wp-admin/plugins.php]] for the status of the plugins (and configuration/activation, etc.)
@@ Line 5: / Line 5: @@
   - use Debian package(s) as feasible, otherwise ...
   - download .zip file
-    - generally WordPress wants to use FTP(S) to access the web site, place the .zip file there, and extract and install it
+    - to find out where to download from:
-      - in general and as feasible, don't do that, but rather download the .zip file directly
         - on the plugins page [[https://berkeleylug.com/wp-admin/plugins.php]]
         - generally --> (View details / Visit plugin site -->) WordPress.org Plugin Page / Plugin Homepage / Visit plugin site
         - and then hopefully a download link on such page or reasonably accessible thereunder - but alas, some sites/pages/plugins don't offer that.
-    - extract and place in suitably named directory (generally same name as plugin) under /var/lib/wordpress/wp-content/plugins/
+    - place the .zip file on host, and extract and install it
-      - only use/create directory names that start with matching * file glob for plugins to actually show in WordPress (e.g. otherwise use names starting with . for temporary purposes)
+      - extract and place in suitably named directory (generally same name as plugin) under /var/lib/wordpress/wp-content/plugins/
-      - be sure to use appropriate ownerships/permissions
+        - note directories under there don't by their name determine the name of the plugin as it shows in WordPress, but rather the contents determine the name by which it shows in WordPress
-      - note directories under there don't by their name determine the name of the plugin as it shows in WordPress, but rather the contents determine the name by which it shows in WordPress
+          - e.g. if there are two differently named directories with otherwise same content, both will show as two separate plugins with same name in WordPress and may be acted upon and then show, e.g. different status or versions, etc. - so don't do that
-        - e.g. if there are two differently named directories with otherwise same content, both will show as two separate plugins with same name in WordPress and may be acted upon and then show, e.g. different status or versions, etc. - so don't do that
+        - only use/create directory names that start with matching * file glob for plugins to actually show in WordPress (e.g. otherwise use names starting with . for temporary/hidden purposes)
-      - reload [[https://berkeleylug.com/wp-admin/plugins.php]] to get updated status, Activate/Deactivate, use/review Settings, etc. as relevant and appropriate
+        - be sure to use appropriate ownerships/permissions
+          - www-data:www-data and writable by www-data allows WordPress to update via [[https://berkeleylug.com/wp-admin/plugins.php]]
+          - root:root and not writable by www-data to lock it down (may also be sym linked to location on /usr to be mostly mounted ro)
+  - alternatively one can (attempt to) update via ''update now'' link for the plugin on [[https://berkeleylug.com/wp-admin/plugins.php]]
+    - generally preferable, as feasible, to not do that but instead manually download the .zip file and install as noted further above (notably for security reasons, etc.), but sometimes may not be feasible (e.g. unable to determine location to manually download .zip file from)
+    - using approach ''update now'' for the plugin on [[https://berkeleylug.com/wp-admin/plugins.php]], WordPress attempts to locally change the files
+      - see information on ownerships/permissions further above
+      - if that fails it defaults to failover attempting (or prompting to attempt) via FTP(S) to access and alter the files on web site that way
+        - by adding ''define('FS_METHOD', 'direct');'' to /etc/wordpress/config-berkeleylug.com.php we disable WordPress from attempting FTP(S), this may be useful for diagnostic purposes (e.g. what it's failing to update/write/etc. and where)
+  - reload [[https://berkeleylug.com/wp-admin/plugins.php]] to get updated status, Activate/Deactivate, use/review Settings, etc. as relevant and appropriate
+====== Updating Themes ======
+  - rather similar to Plugins as noted above, except:
+    - (re)load [[https://berkeleylug.com/wp-admin/themes.php]] for status, etc.
+    - /var/lib/wordpress/wp-content/themes instead of /var/lib/wordpress/wp-content/plugins/
+    - There may not be a "download" or download for .zip file or equivalent.