Previous1Next
Benjamin
Posts: 34
Plugins: 2
Downloads: 3.7k

When I try to use the automatic update from version 2.2 to 2.3 I get a XSS error message and the following php-errors:

Notice (8) Undefined property: update_class::$gpLayout
    in: /home/www/web398/html/gpEasy/include/tool/gpOutput.php
    on line: 539 Notice (8) Undefined variable: theme_stylesheet
    in: /home/www/web398/html/gpEasy/include/tool/gpOutput.php
    on line: 1668 Notice (8) Undefined variable: theme_stylesheet
    in: /home/www/web398/html/gpEasy/include/tool/gpOutput.php
    on line: 1668 Notice (8) Undefined variable: theme_stylesheet
    in: /home/www/web398/html/gpEasy/include/tool/gpOutput.php
    on line: 1668

 

3 years ago#2553
Josh S.
Posts: 1.5k
Themes: 16
Plugins: 15
Downloads: 99k

It's a bit of a chain of events that causes this. The debugging setting in the install script results in a notice for an undefined variable which prevents the javascript from executing, which prevents the client side form validation, which results in the xss detection, preventing gpEasy from upgrading. Two things

1) Just for reassurance, this problem has been fixed in 2.3

2) Getting it to work in 2.2 is very simiple. Just remove the define('gpdebug',true); in /include/install/update.php

Sorry about the trouble.

The intention was to allow for more information to be displayed in case of an error during the update process, but it resulted in the update failing because of small & insignificant notices.

Edited: 3 years ago#2554
Benjamin
Posts: 34
Plugins: 2
Downloads: 3.7k

Thank you, that works fine.

Just in case someone else has this problem and does not know immediately what to change, this is how the changed part at the beginning of the file should look like:

<?php

define('is_running',true);

//old entry point
if( defined('gpdebug') ){

    $dir = dirname(dirname(__FILE__));
    require_once($dir.'/common.php');
    common::EntryPoint(0,'update.php');

//new entry poing
}else{
//    define('gpdebug',true);
    require_once('../common.php');
    common::EntryPoint(2,'update.php');
}

3 years ago#2555

 

FYI: I made that change (commenting out the debug line) and got past that point,
 but after some screens got this:
 
  • Oops, there was an error while trying to process the downloaded package. (3)
  • /_old_include-7251
    /addons/_old_Example-7251
    /addons/_old_Multi Site-7251
    /themes/_old_Black Header-7251
    /themes/_old_One_Point_5-7251
I clicked "next step", and it completed correctly (I hope).  Seems to be okay.
 
 
3 years ago#2607
Josh S.
Posts: 1.5k
Themes: 16
Plugins: 15
Downloads: 99k

You should be good. The upgrade process is fairly involved and is constantly making sure everything is working properly before it will finalize the upgrade. If anything doesn't go as planned, the current step will stop to prevent any unwanted results. Depending on the step, you can normally continue on with the upgrade process without having to start over, which sounds like is what happened in your case. So yeah, it should be all set.

3 years ago#2608
Previous1Next

gpEasy News

4.3.2
2/18/2014

The final release of gpEasy 4.3.2 is now available. This is primarily a third-party package ... Read More

4.3 Final
11/4/2013

The wait is over. The final release of gpEasy 4.3 brings some exciting new features ... Read More

More News

Communics Communication Designers

We convert your static HTML website to gp|Easy with ease. We are specialised in small websites build with the latest web technologies and design trends. O yeah, and responsive of c...

Find out more about gpEasy's Provider Spotlight

Log In

  Register