Upgrade v1.1.1 --> v2.2.2 r3

Markus FFM · 2017-10-18 06:45:51

Hi,

I have downloaded the latest v2.2.2 r3 and wonder how to proceed for upgrading from version 1.1.1.

My theory according to the changelog:

do: **v1.2.0** (2017-06-30)
skip: **v1.2.1** (2017-07-07)
skip: **v1.2.2 Release 1** (2017-07-18)
skip: **v1.2.2 Release 2** (2017-07-31)
do: **v1.2.2 Release 3** (2017-09-10)

Assuming to find the required directories/files for the 1.2.0 procedure in the 1.2.2 r3 download as well.

Thanks,
Markus

rod barbee · 2017-10-18 07:37:34

double check with the readme.txt file that comes with the download.
I think the some things like admin, designer, framework, and publisher folders get replace somewhere in there, possibly 1.2.2 release 1

Matthew · 2017-10-18 11:42:00

If it's too much hassle reconciling the various changelogs, then simply update the entire application, preserving your backlight/data and backlight/custom folders.

The only reason we itemize folders and files during updates is to shorten uploads for users when only a specific folders need changing.

Matthew · 2017-10-18 11:43:36

You might also want to download the last updates for the Okapi modules as well, just to ease your transition into Pangolin, as these modules are not included in the 1.2.x downloads.
http://community.theturninggate.net/vie … hp?id=7769

Markus FFM · 2017-10-19 05:28:28

Ok, I now managed to destroy my galleries.

First I replaced the folders from the Okapi 1.2x download.
--> I think already at this stage the problems occured.

Then I copied from the v2.2.2 r3 download
- the folder TTG-Publisher.lrplugin
- all folders from the /backlight folder except /data and /custom (and also not the okapi only ones in /modules)
- I did not touch any file in the /data and /custom folder
- I did not touch index.php, env.php.skel, config.php in folder /backlight
- I did not touch index.php and .htaccess on top level
- I cleared the template cache

You can see the result here:

http://www.entscheidend-is-aufm-platz.com/ttg/

The lowest level of a single gallery seems still to work, all higher levels throw errors (+ the "slightshow" gallery that used to be hidden in navigation is shown there and you can access is as a gallery while it used only to show up as slideshow.

Examples:
works: http://www.entscheidend-is-aufm-platz.c … 016_03_08/

not found: http://www.entscheidend-is-aufm-platz.c … 016_02_08/

works not: http://www.entscheidend-is-aufm-platz.c … ries/2016/

Thanks for checking,
Markus

Last edited by Markus FFM (2017-10-19 05:30:23)

rod barbee · 2017-10-19 05:40:42

looks like you might have removed some modules without replacing them? Like Standard-Album-Set. At least this is what the error message is indicating.
Do you still have standard-album-set in your /backlight/modules/ folder?
See Matt's response at #4 above and try uploading the Okapi modules.

Markus FFM · 2017-10-19 05:53:35

Hi Rod,

I copied the complete folder but for some reason the 4 single files in the folder have been skipped.

I looks much better now, some hick-ups still that might be wrong configurations from my side, but looks a bit strange, e.g. on main page http://www.entscheidend-is-aufm-platz.com/ttg/ the "Fotos" menu has only 1 level while on "Suchen" page http://www.entscheidend-is-aufm-platz.c … ht/search/ the "Fotos" menu has 2 levels.

But the main problem is fixed.

Thanks for that,
Markus

rod barbee · 2017-10-19 06:00:48

The reason for the difference in the level of menus could be that the page templates for those pages are using different Menu Sets.
Edit the page templates and see what Menu Sets are being used.

Markus FFM · 2017-10-19 06:40:54

I have only the default menu set and there the "Fotos" menu is set to "Descend up to 2 levels".

On the page templates I cannot find any option to select different Menu Sets, maybe because I have only the default one?

rod barbee · 2017-10-19 06:49:29

when I look at the two pages you link to, the "Fotos" menu looks the same on both pages. they both descend one level below "fotos"

Markus FFM · 2017-10-20 02:17:03

I can reproduce:

Opera v48/Windows:
"Fotos" menu always shows only first level. You can see the arrow to the next level, but it does not work.

IE latest version/Windows:
"Fotos" menu always shows only first level. You can see the arrow to the next level, but it does not work.

Firefox/Windows: On "Suchen" screen and single album level "Fotos" menu shows two levels.
On all other screens "Fotos" menu always shows only first level.

I saw that single albums and search screen use as only pages the same template (Standard Album Template).

I can only assume, that in this template there are whatever settings, that allow the second menu level to work, while in other templates there are whatever settings that makes second menu not to work.

Probably other browsers as Firefox render a bit different so they also disable the second menu level on pages using the Standard Album Template.

As it used to work before, there must have been something in the update that broke the layout.

rod barbee · 2017-10-20 04:06:30

I'm using Firefox in Windows and the menus on all of your pages are behaving the same for me (Home, Search, about, contact, album sets, and albums)
Try clearing your browser cache and look again. I checked in Firefox, Opera, Chrome, and Edge

I saw that single albums and search screen use as only pages the same template (Standard Album Template).
I can only assume, that in this template there are whatever settings, that allow the second menu level to work, while in other templates there are whatever settings that makes second menu not to work.

No. Standard Album Template is an album template. It uses a page template. The page template is where the Menu Set is assigned.

Markus FFM · 2017-10-20 05:17:00

Seems like this cannot be solved.

To be triple sure I installed a new browser that never has been installed on my machine and it behaves the same as all browsers except Firefox on some pages that use Standard Album Template, only the first menu level is functional.

rod barbee · 2017-10-20 06:30:04

We can only guess. It would help to see your set up. Feel free to post or email backlight guest login credentials.

Matthew · 2017-10-20 11:06:42

I'm looking at your menus. I can see that the second level menu is there, both in source code and on the page. On the page, it's in the correct location; I can get it to outline. I'm just trying to figure out why it's not visible ...

Are you running any customizations, i.e. custom CSS, PHPlugins, etc.?

I see you're also running okapi still. I reckon the problem will remedy itself when you switch to pangolin.

Matthew · 2017-10-20 11:13:38

Found it. Set this CSS via custom:

nav ul ul li { overflow: visible; }

When you update to pangolin, you can discard this fix.

Markus FFM · 2017-10-28 19:17:53

Yes, this fixed it. Thanks for that.

Rgds
Markus

Samoreen · 2017-10-29 23:31:10

Markus FFM wrote:

Then I copied from the v2.2.2 r3 download

v 2.2.2 R3. What's that ?

Last edited by Samoreen (2017-10-29 23:31:28)

Community @ The Turning Gate

#1 2017-10-18 06:45:51

Upgrade v1.1.1 --> v2.2.2 r3

#2 2017-10-18 07:37:34

Re: Upgrade v1.1.1 --> v2.2.2 r3

#3 2017-10-18 11:42:00

Re: Upgrade v1.1.1 --> v2.2.2 r3

#4 2017-10-18 11:43:36

Re: Upgrade v1.1.1 --> v2.2.2 r3

#5 2017-10-19 05:28:28

Re: Upgrade v1.1.1 --> v2.2.2 r3

#6 2017-10-19 05:40:42

Re: Upgrade v1.1.1 --> v2.2.2 r3

#7 2017-10-19 05:53:35

Re: Upgrade v1.1.1 --> v2.2.2 r3

#8 2017-10-19 06:00:48

Re: Upgrade v1.1.1 --> v2.2.2 r3

#9 2017-10-19 06:40:54

Re: Upgrade v1.1.1 --> v2.2.2 r3

#10 2017-10-19 06:49:29

Re: Upgrade v1.1.1 --> v2.2.2 r3

#11 2017-10-20 02:17:03

Re: Upgrade v1.1.1 --> v2.2.2 r3

#12 2017-10-20 04:06:30

Re: Upgrade v1.1.1 --> v2.2.2 r3

#13 2017-10-20 05:17:00

Re: Upgrade v1.1.1 --> v2.2.2 r3

#14 2017-10-20 06:30:04

Re: Upgrade v1.1.1 --> v2.2.2 r3

#15 2017-10-20 11:06:42

Re: Upgrade v1.1.1 --> v2.2.2 r3

#16 2017-10-20 11:13:38

Re: Upgrade v1.1.1 --> v2.2.2 r3

#17 2017-10-28 19:17:53

Re: Upgrade v1.1.1 --> v2.2.2 r3

#18 2017-10-29 23:31:10

Re: Upgrade v1.1.1 --> v2.2.2 r3

Board footer