Wordpress: Difference between revisions

From Bitpost wiki
No edit summary
Line 2: Line 2:


I always update Wordpress when an update is available, straight in the admin panel with no backup.
I always update Wordpress when an update is available, straight in the admin panel with no backup.
''''CACHING WILL KILL YOU THOUGH.''''  Remember to restart apache AFTER pressing the auto-update button:
sudo /etc/init.d/apache restart


==== Manual ====
==== Manual ====
Wordpress release quality has gone to shit in 2018-2019 and I've had to do the manual installation clobber, THIS SUCKS but whatever:
 
Usually caching is to blame when something goes wrong (see above).  But if you need to dig deeper, you can try a manual update (ie, 'clobber'):


   # FIRST DISABLE ALL PLUGINS yes this will FUCK YOU UP OTHERWISE
   # FIRST DISABLE ALL PLUGINS yes this will FUCK YOU UP OTHERWISE
Line 13: Line 18:
   🌵 m@bitpost  [~/development/bitpost.com/htdocs/news] unzip latest.zip
   🌵 m@bitpost  [~/development/bitpost.com/htdocs/news] unzip latest.zip
   🌵 m@bitpost  [~/development/bitpost.com/htdocs/news] sudo chown -R apache:apache .
   🌵 m@bitpost  [~/development/bitpost.com/htdocs/news] sudo chown -R apache:apache .
 
   🌵 m@bitpost  [~/development/bitpost.com/htdocs/news] sudo /etc/init.d/apache restart # RESTART APACHE or shit will be cached
   # RESTART APACHE or shit will be cached!
   
   
  one-liner:
  one-liner:
  cd ~/development/bitpost.com/htdocs/news && wget https://wordpress.org/latest.zip && rm -rf wp-includes wp-admin && unzip latest.zip && sudo chown -R apache:apache .
  cd ~/development/bitpost.com/htdocs/news && wget https://wordpress.org/latest.zip && rm -rf wp-includes wp-admin && unzip latest.zip && sudo chown -R apache:apache . && sudo /etc/init.d/apache restart


=== My themes ===
=== My themes ===

Revision as of 15:59, 12 May 2019

Upgrade

I always update Wordpress when an update is available, straight in the admin panel with no backup.

'CACHING WILL KILL YOU THOUGH.' Remember to restart apache AFTER pressing the auto-update button:

sudo /etc/init.d/apache restart

Manual

Usually caching is to blame when something goes wrong (see above). But if you need to dig deeper, you can try a manual update (ie, 'clobber'):

 # FIRST DISABLE ALL PLUGINS yes this will FUCK YOU UP OTHERWISE
 # worst-case, if things are fubar, rename this folder: wp-content/plugins

 🌵 m@bitpost  [~/development/bitpost.com/htdocs/news] wget https://wordpress.org/latest.zip
 🌵 m@bitpost  [~/development/bitpost.com/htdocs/news] rm -rf wp-includes wp-admin
 🌵 m@bitpost  [~/development/bitpost.com/htdocs/news] unzip latest.zip
 🌵 m@bitpost  [~/development/bitpost.com/htdocs/news] sudo chown -R apache:apache .
 🌵 m@bitpost  [~/development/bitpost.com/htdocs/news] sudo /etc/init.d/apache restart # RESTART APACHE or shit will be cached

one-liner:
cd ~/development/bitpost.com/htdocs/news && wget https://wordpress.org/latest.zip && rm -rf wp-includes wp-admin && unzip latest.zip && sudo chown -R apache:apache . && sudo /etc/init.d/apache restart

My themes

bitpost.com/news

Here i use a very jacked theme:

~/development/bitpost.com/htdocs/news/wp-content/themes/mdm_veryplaintxt

Custom widgets, fonts, etc:

~/development/bitpost.com/htdocs/news/wp-content/themes/mdm_veryplaintxt/functions.php

CSS:

~/development/bitpost.com/htdocs/news/wp-content/themes/mdm_veryplaintxt/style.css

To play with fonts:

  • go to google fonts and find some cool ones
  • adjust functions.php to load the new ones
  • adjust style.css to use them; you should consider font family, size, and weight of at least these 4 things:
body
#content h2
pre
#sidebar ul
  • restart apache!