Comments (7)
Apparently the update needs to happen in two steps....first to 1.35, then to 1.39. I have version 1.35 installed in the public_html/wiki_debug directory. The old version is still in public_html/wiki. They are sharing the same database, which has been updated for 1.35. The old database has been backed up to both sql and xml backup files,. The old files are also backed up, but since I did it with 'cp', I suspect the permissions might have been messed with in the backup.
I had all kinds of problems getting 1.35 running....mostly "Internal Server Errors", with little other information, even after turning on all kinds of PHP debugging flags in LocalSettings.php and php.ini. The issue turned out to be permissions problems on the php files (they were group readable, need to be mode 644) and directories (again, group readable, needed to be mode 755). I had to log into spedas.org as root (not spedas!) in order to be able to see the apache2 error logs, which called out the permissions issues. Now, after correcting the permissions, it seems to be working (though the code formatting extension is disabled, until I upgrade all the way to 1.39 or 1.40).
For the second half of the upgrade, I'll take another pair of database backups, and try the tarball rather than the zip file for the mediawiki file installation, and also for backing up the existing files. At least I know now to watch the apache2 logs to diagnose any mysterious problems that come up.
from bleeding_edge.
I couldn't get version 1.39 working properly. The "vector" skin wasn't being applied -- the page contents showed, I could log in, navigate around, etc., but the logo was missing and the styles weren't being applied. No errors showing in the Apache logs, nor any obvious PHP errors in the debug log. There might be some oddity in Hostgator's Apache or PHP config that needs special .htaccess magic or changes to PHP defaults for this version to work.
I've restored the database and wiki files from backups, so we're back at version 1.34 until I can figure out how to do a clean upgrade. Maybe we're better off migrating spedas.org to SSL servers, then trying to upgrade the wiki without any hostgator/cpanel stuff getting in the way.
from bleeding_edge.
OK, trying this again with a bit more caution. I've cloned the production database and site files to spedas.org/wiki_dev, so if I screw something up, it won't affect the production site. Notes from last attempt: pay close attention to file & directory permissions, don't copy the skins directory from the pre-upgrade version; may have to rebuild the localization cache (using maintenance/rebuildLocalizationCache.php), check error_log in the wiki directory if problems occur, pay closer attention to release notes and upgrade instructions (e.g. specifying the logo in LocalSettings.php is done differently in later versions).
from bleeding_edge.
More updates notes: Untar the new files with "tar xvf mediawiki-X.XX.XX.tar" right in public_html, then 'mv' to the target directory. There are some weird permissions if you use "tar xvfp", that resulted in empty directories when I did "cp -R" to install it in public_html. It might be necessary to "chmod 755" the top level directory, but I didn't have to mess with any permissions other than that.
from bleeding_edge.
New way of specifying the logo file in 1.35 and later....instead of setting $wgLogo, you can now set $wgLogos, a map which can specify 1x, 2x, svg, or wordmark versions of the logo. We're just using 1x for now.
## The relative URL path to the logo. Make sure you change this from the default,
## or else you'll overwrite your logo when you upgrade!
#$wgLogo = "$wgScriptPath/images/2/29/Wiki_logo_draft.jpg";
$wgLogos = [ '1x' => "$wgScriptPath/images/2/29/Wiki_logo_draft.jpg" ];
from bleeding_edge.
I figured out why some of my attempts didn't work: I had been getting errors because some PHP files were group writeable. I tried to fix this with something like find . -name \*.php -exec chmod 644 {} \;
(i.e. change all PHP files in the entire directory tree to mode 644). Annoyingly, there's a directory called less.php -- if you change it to mode 644 (instead of 755), it breaks the site.
from bleeding_edge.
Upgrade complete! We are now at mediawiki version 1.40.2, the latest stable version, and everything appears to be in working order. The current state of the files & database are backed up in ~/wiki_backups.
Going forward: There's now a development version of the wiki site, so we can try making changes without worrying about breaking the production site. It's in the wiki_dev directory, and it has its own database spedas_wiki_dev (mysql user spedas_wikidev), so it's completely isolated from the production site.
from bleeding_edge.
Related Issues (20)
- Update MMS sunlight masking tables
- Implement improved THEMIS-E FGM spin axis calibration HOT 1
- Implement contour lines in tplot specplots
- MMS FEEPS bad eye removal flag?
- Update and recalibrate FGM L2 with new files through Feb 2024 HOT 1
- Missing VIRTUAL attributes for L2 ESA CDFs
- Process apid 407 memory dumps to more human-readable format
- pser not properly calibrated HOT 1
- Manual reprocessing for THEMIS-A, Mar 26 2024 HOT 1
- Corrupted MagStar GMAG CDFs from cdf_make_vars HOT 6
- Loading KOMPSAT data in IDL 9.0? HOT 1
- Spin tone in FGL-DSL data when loading multiple days of data HOT 1
- SPEDAS 6.1 release needed HOT 2
- Problem with SPDF virtual functions in SPEDAS executables HOT 1
- Add SMART GMAG data
- Develop code to infer THEMIS-E Bz component from Bx, By and particle data
- Develop ICCR for THEMIS-E to support determination of Bz component from particle data
- Missing GOES data in summary plots HOT 1
- Reprocess THEMIS AE index May 10-11 with Alaska stations HOT 1
- PHP issues on UCLA mirror of themis web site HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bleeding_edge.