Re: convert.php / Update from 0.11 -> 0.12
Posted: 24 Nov 2015, 00:32
Mobile working now. I want to address the other issue you had referred to. I did nothing outside of the normal checking of boxes. Did the upgrade overwrite that issue?
X3 Photo Gallery Support Forums
https://forum.photo.gallery/
The upgrade would not affect that. If it's working now anyway, it would be pointless to try to diagnose something that can't be diagnosed any longer.swamphox wrote:Mobile working now. I want to address the other issue you had referred to. I did nothing outside of the normal checking of boxes. Did the upgrade overwrite that issue?
# Get X3 config
require_once "./app/x3.config.inc.php";
global $x3_config;
$x3_config = getX3Config();
Sorry, its a bit clumsy, but its the only method ... Basically its just a page/settings converter, so you still need to upgrade BEFORE your run the convert ... Then run the convert.php to convert the pages and settings in your content folder.Eightkill wrote:Hy, I'm surely dumb but i don't get it.
I didn't know that content/services, content/sitemap, content/json, content/feed have become obsolete en can be deleted.mjau-mjau wrote:4. Finally, you should delete content/services, content/sitemap, content/json, content/feed and content/custom
5. Upload the content/custom from the latest release (into content/custom)
Exactly.Martin wrote:FOUND IT:
I think the answer is YES, because all their info is now stored in config/config.user.json
... and these folders have become virtual routes in new X3, so no need to maintain folder placeholders for them any more since they were never supposed to be edited anyway.Martin wrote:I didn't know that content/services, content/sitemap, content/json, content/feed have become obsolete en can be deleted.
This is part of the system logic and how pages work, but I can understand that looked strange for an outsider.Martin wrote:
- folder 404 has page.json
- folder audio has 404.json
- folder favicon has 404.json
- folder logo has 404.json
Sound logical... nowmjau-mjau wrote: Audio, favicon and logo with "404.json" are not actual pages, but content containers, thus they should create a "404 page not found" response if accessed directly. The 404 folder however, is an actual page with content, settings and data stored in page.json.
The recommendation of making the logo approximately twice as large as it is displaying is a recommendation regardless of how the logo is actually displaying, so I am not sure how that can be broken.Eightkill wrote:The managing of the logo seems to have changed. The recommandation of "get a logo about twice the size than the one u want", seems to be broken. The logo appears smaller on 0.12 with the same settings. Even by modifying the width in the CSS, it's still the same so i guess i have to recreate a bigger one in order to have the same size as before ?
To be honest, I am not quite sure what we are discussing ... Sure, there can be minor changes as to what was before and what is now, because I need to adjust defaults based on what I feel is a good average for a NEW X3 installation. Furthermore, I can't anticipate what your logo will look like, and what layout you are using ... A logo could be tall or short, narrow or fat.Martin wrote:I was under the same impression that the logo is now smaller.