phpwcms Support Forum

While copying things like index.php a.s.o from older revisions you leave control on the system.

1. Old system (backed)
2. New above
3. upgrade
4. reinstall templates


In case of trouble:

compare dbstructure for missing fields / Indexes.

Leaving this means leaving any redrivable system.

DF6IH wrote:While copying things like index.php a.s.o from older revisions you leave control on the system.

1. Old system (backed)
2. New above
3. upgrade
4. reinstall templates


In case of trouble:

compare dbstructure for missing fields / Indexes.

Leaving this means leaving any redrivable system.

Hello!
I did that/this...
1. I have backup of old system
2. I copied new files over the old files
3. first i upgraded DB (maybe i shouldn't do it first?). I didn't run setup/upgrade.php. Is this necessary to run after manually DB updating ...?
4. template files are in place. How do you mean "reinstall templates"? Do I need to do something in backend?

V1.4.2 -> V1.4.7

Please read this: Releases

And have a look into the generated HTML core: "template/inc_js/jquery.js" isn´t the right adress. -> Init Mootools/jQuery Library

Knut

flip-flop wrote:V1.4.2 -> V1.4.7

Please read this: Releases

And have a look into the generated HTML core: "template/inc_js/jquery.js" isn´t the right adress. -> Init Mootools/jQuery Library

Knut

OK, I've checked DB structure before upgrade,... It was already updated comparing to /setup/update_sql/22__1.4_to_1.5.sql, so this is done

I tried to make JS image slider working, but I failed to do so. Right now, I will disable it, until I find solution.


But, what is more concerning me, is why background image wasn't displayed.
That image is set in Pagelayout - field background "image".

Eventually, I revert to old files in include/inc_front, and it worked, background image appeared (http://www.kompas.ba/cms2)...
So, problem was in rendering Pagelayout data with new include/inc_front files?

Any advise?

OK, I found why background image from Pagelayout didn't appeared.
I made comparing old (1.4.2) and new (1.4.7) front.func.inc.php.

Look like there is more lines of code in old front.func.inc.php regarding pagelayout, so I took that part and replaced it in new front.func.inc.php.
Files with replaced part are here:
new front.func.inc.php crop ...http://www.kompas.ba/new_front.txt
old front.func.inc.php crop ...http://www.kompas.ba/old_front.txt

Any comments?
What do you think, what will my action do? Will it break something up?

And, do you have better solution?

Thanks in advance!

don't use old style of body loaded js any longer or custom functions that overwrite onload function. This is crap and there is no need as long you use jQuery. There you have the ready() event (like the domready in MooTools)

Oliver Georgi wrote:don't use old style of body loaded js any longer or custom functions that overwrite onload function. This is crap and there is no need as long you use jQuery. There you have the ready() event (like the domready in MooTools)

OK, I think I'm give up of this upgrade...
Already spent 3 days of trying to do successful upgrade... and always new problem arise. I found that Mootools are not working at all at upgraded version...
And also, I'm doing editing of php files, what I really don't wanna do (eventually it will do more damage - for example, next upgrade).

So,
I'm gonna install new version, and then upload DB data from old version.
old DB already have same structure as new one (I made DB upgrade manually, and I'm sure that it is the same), so import should be smooth
Files are not problem,... i will leave filearchive and content directories as it is now...

Hope this scenario is OK?

There was no change with the update regarding MooTools. But you have to decide to use MooTools 1.1 otherwise it will fail!

Always: use FireFox in combination with Web Developer Extension to trace JavaScript problems and FireBug to check some more things. That is save on Mac and Windows. For Chrome Web Developer extension is available too now. JavaScript seems to be your problem and how you load which and when.

Oliver Georgi wrote:There was no change with the update regarding MooTools. But you have to decide to use MooTools 1.1 otherwise it will fail!

Always: use FireFox in combination with Web Developer Extension to trace JavaScript problems and FireBug to check some more things. That is save on Mac and Windows. For Chrome Web Developer extension is available too now. JavaScript seems to be your problem and how you load which and when.

You are right!
JS was problem,... I needed to delete old jquery scripts from template/inc_js (that js templates are now in lib folder). After that Image slider worked! Also tabs (simpletabs) is working
I changed the way how background is rendered. I included bg code in template instead in pagelayout. So this is fixed also

I think I can call this upgrade successful.

Thank you on your help and your advises!

My web hoster today has given the following notice.

The maintenance works will have effect on the php version, which will be updated from version 5.2.12 to 5.2.14.

Changelogs are available at
http://www.php.net/ChangeLog-5.php#5.2.13
http://www.php.net/ChangeLog-5.php#5.2.14

Please check, if your scripts are compatible with the php version mentioned above.

Are they?

Yes, the jump was from 5.2 to 5.3 in which ereg is deprecated.

i am on r402 and want to update to r411.
is this possible and is there any working solution on this topic?

der hausmeister

r412 is the latest official.

Backup. Update files. Backend login. Ready.

worked without problems – thanks for your help.