1AND1 Install Gallery3 RC1 Issue

I know that only some few use 1AND1 hosting. I had G3 running on 1AND1 but had to rebuild my machine and when i tried to do a fresh install i end up with a nice white screen. any ideas what i need to do?

this is the exact steps i followed:
1. uploaded G3 RC1 to 1AND1 /gallery3 and unzipped
2. created 'var' and set to 777
3. setup MySQL (note that 1AND1 is using php5.2.13 as of today but not 5.2.3 yet)
4. edited .htaccess by adding 'AddType x-mapp-php5 .php' to top of file
5. browsed to http://mydomain.com/gallery3/install
6. copied db name, db host, db user to Gallery3 form that appeared and also set prefix to G3_
7. after going to the next screen i went into my gallery3
8. white page appeared with NO ERRORS

what should i do to resolve this?

thanks,

billy

William Johnson - Billy
Statesboro, GA. 30461 USA

As Floridave and Nivekiam have decided 1&1 is just too much trouble, you might want to ask SergeD, the 1&1 guru, to have a look for you

BTW PHP 5.2.13 is fine and up to date … unlike their infamous Apache 1.3.

--
dakanji.com

hello,

this is some of teh errors errors i got:

Kohana_Exception [ Framework Error ]: The requested views, admin.html, could not be found

1.

SYSPATH/core/Kohana.php[ 812 ]
807 if ($found === NULL) 808 { 809 if ($required === TRUE) 810 { 811 // If the file is required, throw an exception 812 throw new Kohana_Exception('The requested :resource:, :file:, could not be found', array(':resource:' => __($directory), ':file:' =>$filename)); 813 } 814 else 815 { 816 // Nothing was found, return FALSE 817 $found = FALSE;
2.

SYSPATH/libraries/View.php[ 83 ] » Kohana_Core::find_file( arguments )

directory

string(5) "views"

filename

string(10) "admin.html"

required

bool TRUE

78 public function set_filename($name, $type = NULL)
79 {
80 if ($type == NULL)
81 {
82 // Load the filename and set the content type
83 $this->kohana_filename = Kohana::find_file('views', $name, TRUE);
84 $this->kohana_filetype = EXT;
85 }
86 else
87 {
88 // Check if the filetype is allowed by the configuration

3.

SYSPATH/libraries/View.php[ 49 ] » View_Core->set_filename( arguments )

name

string(10) "admin.html"

type

NULL

44 public function __construct($name = NULL, $data = NULL, $type = NULL)
45 {
46 if (is_string($name) AND $name !== '')
47 {
48 // Set the filename
49 $this->set_filename($name, $type);
50 }
51
52 if (is_array($data) AND ! empty($data))
53 {
54 // Preload data using array_merge, to allow user extensions

4.

MODPATH/gallery/libraries/MY_View.php[ 56 ] » View_Core->__construct( arguments )

name

string(10) "admin.html"

data

NULL

type

NULL

51 * Override View_Core::__construct so that we can set the csrf value into all views.
52 *
53 * @see View_Core::__construct
54 */
55 public function __construct($name = NULL, $data = NULL, $type = NULL) {
56 parent::__construct($name, $data, $type);
57 $this->set_global("csrf", access::csrf_token());
58 }
59
60 /**
61 * Override View_Core::render so that we trap errors stemming from bad PHP includes and show a

5.

MODPATH/gallery/libraries/Admin_View.php[ 30 ] » View->__construct( arguments )

name

string(10) "admin.html"

25 * @param string $name view name
26 * @param string $theme_name view name
27 * @return void
28 */
29 public function __construct($name) {
30 parent::__construct($name);
31
32 $this->theme_name = module::get_var("gallery", "active_admin_theme");
33 if (identity::active_user()->admin) {
34 $this->theme_name = Input::instance()->get("theme", $this->theme_name);
35 }

6.

MODPATH/user/controllers/admin_users.php[ 22 ] » Admin_View_Core->__construct( arguments )

name

string(10) "admin.html"

17 * along with this program; if not, write to the Free Software
18 * Foundation, Inc., 51 Franklin Street - Fifth Floor, Boston, MA 02110-1301, USA.
19 */
20class Admin_Users_Controller extends Admin_Controller {
21 public function index() {
22 $view = new Admin_View("admin.html");
23 $view->content = new View("admin_users.html");
24 $view->content->users = ORM::factory(
25 $view->content->groups = ORM::factory("group")->order_by("name", "ASC")->find_all();
26 print $view;
27 }

7.

{PHP internal call} » Admin_Users_Controller->index()
8.

MODPATH/gallery/controllers/admin.php[ 57 ] » call_user_func_array( arguments )

function_name

array(2) (
0 => object Admin_Users_Controller(1) {
private theme => NULL
}
1 => string(5) "index"
)

parameters

array(0)

52
53 if (!method_exists($controller_name, $method)) {
54 throw new Kohana_404_Exception();
55 }
56
57 call_user_func_array(array(new $controller_name, $method), $args);
58 }
59
60 private static function _reauth_check() {
61 $session = Session::instance();
62 $last_active_auth = $session->get("active_auth_timestamp", 0);

9.

{PHP internal call} » Admin_Controller->__call( arguments )

controller_name

string(5) "users"

args

array(0)

10.

SYSPATH/core/Kohana.php[ 330 ] » ReflectionMethod->invokeArgs( arguments )

object

object Admin_Controller(1) {
private theme => NULL
}

args

array(2) (
0 => string(5) "users"
1 => array(0)
)

325
326 // Start the controller execution benchmark
327 Benchmark::start(SYSTEM_BENCHMARK.'_controller_execution');
328
329 // Execute the controller method
330 $method->invokeArgs($controller, $arguments);
331
332 // Controller method has been executed
333 Event::run('system.post_controller');
334
335 // Stop the controller execution benchmark

11.

{PHP internal call} » Kohana_Core::instance( arguments )

0

NULL

12.

SYSPATH/core/Event.php[ 208 ] » call_user_func_array( arguments )

function_name

array(2) (
0 => string(6) "Kohana"
1 => string(8) "instance"
)

parameters

array(1) (
0 => NULL
)

203 Event::$data =& $data;
204 $callbacks = Event::get($name);
205
206 foreach ($callbacks as $callback)
207 {
208 call_user_func_array($callback, array(&$data));
209 }
210
211 // Do this to prevent data from getting 'stuck'
212 $clear_data = '';
213 Event::$data =& $clear_data;

13.

APPPATH/Bootstrap.php[ 67 ] » Event_Core::run( arguments )

name

string(14) "system.execute"

62
63// End system_initialization
64Benchmark::stop(SYSTEM_BENCHMARK.'_system_initialization');
65
66// Make the magic happen!
67Event::run('system.execute');

14.

DOCROOT/index.php[ 91 ] » require( arguments )

William Johnson - Billy
Statesboro, GA. 30461 USA

hello,

why does 1AND1 bother you so? everytime i post for 1AND1 help you get upside down. do you live on this client and you must read every post or just look out for 1AND1 post.

SergeD and myself are not the only ones using 1AND1.

what is interesting is that Gallery3 is the only appz that gives me trouble on 1AND1. if it can be manually adjusted to work on 1AND1 why not design flexiblilty into G3 to allow easy implementation on the host of the USERS chosing, good or bad? are you (they) trying to get every inch-pound of torque even at the cost of additional users?

what does 'the end of it' mean? if you have the 'almighty power', band me from Gallery3 and make your day.

try to be more pleasant.

later,

William Johnson - Billy
Statesboro, GA. 30461 USA

hello ilikebacon,

I will try and get back to you. thanks,
billy

William Johnson - Billy
Statesboro, GA. 30461 USA

I'll also confirm these changes work on 1&1. I've just gotten into G3RC by using them. Thank you ilikebacon!

ATTENTION Gallery3 'think-tanker's':

Please consider this. Would it not make sense to include these required changes into Gallery3 code to allow 1AND1 (or similar host) users to easily setup G3? it would easily fix an install/upgrade issue, allow the product to be more widely used and remove much of the 1AND1 email related 'noise'. this has been a issue with some of Gallery3 users for a few years now (on both sides of the users opinions).

It seems that the old 'Apache 1.x will not work . . . End of the story' argument is not exactly correct. Now i am sure that the newer Apache 2.x is better but . . .

Sincere thanks to all,

billy

William Johnson - Billy
Statesboro, GA. 30461 USA

What you are saying is that you want the developers of G3 to spend time and effort making sure the program works on a version of Apache which the Apache Foundation itself strongly advises people not to use and which they, the people who wrote it in the first place, no longer support.

I am struggling to see the slightest shred of sense in wasting time on making sure new software works with obsolete ones.

It is not correct indeed and nobody ever said it will not work. What the position is, is that it is not supported. If you insist on using it, then it is up to you to make it work. Any problems you may face in using it is your issue based on your choice to use it.

Just that apart from other users who have made the same choice as you, any queries you may have will go unanswered. Not a big deal as long as you do it with your eyes open.

Since a way to make it work has been posted, put it up for others to find in future. However, be prepared for when an upgrade to G3 breaks your gallery in future. This is inevitable and hopefully SergeD or someone else who prefers to use Apache 1.x will help you get it back up.

--
dakanji.com

I can confirm this is a 1and1 apache problem and that they won't/can't change to apache 2. I solved it by actually setting up G3 on another hosting company ( and also solved lots of G2 theme problems cauing me grief!!)

Peter