(Should these early-adopter reports be here?)
Upgrading from 3.1.2 to 3.2, Website Health Check says:
File Name: /data/other/plugins.xml 0644 Not Writeable - Error!
and I have to chmod 0666 as a minimum to clear the error.
Why does it have to be world-writeable? It's owned by the server user.
That is interesting. Was cache moved in 3.1 and the updater never worked ?
Yeah thats fine, please report here.
Yeah that should have been fixed to 644, It is fixed in 3.3 already to use GSCHMOD.
Ill add it to 3.2.1
(2013-02-17, 02:24:43)shawn_a Wrote: Yeah that should have been fixed to 644, It is fixed in 3.3 already to use GSCHMOD.
After changing a plugin state (deactivated -> activated), the permissions changed to 0755 (the GSCHMOD (default) value) and the Health Check reports '0755 Writeable - OK'.
In fact, chmod 0700 also shows 'OK', so permissions of 0666 or 07xx satisfy the check ...
It surely doesn't need to be executable. Is a single GSCHMOD value too coarse?
shawn_a Wrote:Was cache moved in 3.1 and the updater never worked ?
- Never touched the cache.
I updated by overwriting /admin/* and /index.php, plus adding new values to /gsconfig.php.
That was in response to Carlos.
We posted at t same time.
The gs chmod overrides the default 755 for data files.
It is probably to coarse but it should be ok.
(2013-02-17, 02:20:49)shawn_a Wrote: That is interesting. Was cache moved in 3.1 and the updater never worked ?
I've taken a quick look at this... The check for existance for (and creation of ) the data/cache dir took place in admin/inc/common.php in GS 3.1.x, but it has been removed for 3.2 in this commit:
Upgrading 3.1.x to 3.2 has no trouble, as data/cache already exists. So the issue is only with 3.0 or older.
Oh yeah that, I do not think n00dleseant to remove the cache one.
The other was chamed because it was trying to create autosave before the data folder exists
Actually we wanted to move these checks out of common , they didn't belong there.
But we never added them to an upgrade process.
Or rather the upgrade process is badly implemented, it is only for certain upgrades, namely ones with the old user file. I have no idea which upgrade this was, its not even noted in the flow.
Does anyone know when data/cache was added ? I cannot seem to nail it down in SVN.
The only functionality the update has is from user.xml to data/users change, and i do not know when that occured either.
We need to figure out and rewrite the upgrade script, to actually do upgrades based on going from x to x
(2013-02-18, 06:46:00)shawn_a Wrote: Does anyone know when data/cache was added ? I cannot seem to nail it down in SVN.
@ Carlos: YES, it happens to me too and it did the same... all works fine now.
@ shawn_a: I got a problem. GS says: "Warning: Server Setup non-Apache"... Apache web server: Microsoft-IIS/7.5 - Error........ What does mean ? Yes I am using IIS server. How can I fix this error?
(This post was last modified: 2013-02-23, 01:44:57 by Carlos.)
(2013-02-22, 20:26:20)D.O. Wrote: I got a problem. GS says: "Warning: Server Setup non-Apache"... Apache web server: Microsoft-IIS/7.5 - Error........ What does mean ? Yes I am using IIS server. How can I fix this error?
If it's a production/public web site AND you're sure that folders containing data (xml files etc) are secured properly, you can disable the warning by inserting this in your gsconfig.php file:
# Disable check for Apache web server, default false
Ok it works good now... thanks! But what do you mean for production/public web site?
That warning means your site is not secure, because we do not support non apache setups. You are responsible for securing your files since you cannot use .htaccess files.
Meaning secure the folders that contains your data or else people can probably grab your user file etc.
Read the requirements and the release notes on the dl page.
And goto health check.
A site in the WWW that can be accessed by any internet user.
That is, not a private test site or in a protected intranet.
(2013-02-12, 04:13:37)shawn_a Wrote: Known Issues:
- Undo link after deleting pages is missing.
- Upgrading from 3.0, data/cache will not be created
Another known issue: slugs in servers with no multibyte extension
Thanks, i am going to try to get this out today.
I confirm what Carlos said... I am using the new GetSimple 3.2 and it needs a patch for the issue "slugs in servers with no multibyte extension"
3.2.1 beta is already out