Recent Topics

1 Dec 15, 2007 00:33    

My b2evolution Version: Not Entered

I am trying to install from scratch and everything works fine until the default plugins attempt to install and freeze up. Any ideas? Here is what I see on my screen:

Multilingual multiuser multi-blog engine.
Installer for version 1.10.3
Current installation: Install menu · PHP info · Go to Blogs · Go to Admin · Online: Manual · Forums
Installing b2evolution tables with sample data
Created table «evo_groups»
Created table «evo_blogusers»
Created table «evo_settings»
Created table «evo_users»
Created table «evo_blogs»
Created table «evo_coll_settings»
Created table «evo_categories»
Created table «evo_posts»
Created table «evo_postcats»
Created table «evo_comments»
Created table «evo_locales»
Created table «evo_antispam»
Created table «evo_sessions»
Created table «evo_usersettings»
Created table «evo_item__prerendering»
Created table «evo_poststatuses»
Created table «evo_posttypes»
Created table «evo_files»
Created table «evo_basedomains»
Created table «evo_useragents»
Created table «evo_hitlog»
Created table «evo_subscriptions»
Created table «evo_bloggroups»
Created table «evo_links»
Created table «evo_filetypes»
Created table «evo_plugins»
Created table «evo_pluginsettings»
Created table «evo_pluginusersettings»
Created table «evo_pluginevents»
Created table «evo_cron__task»
Created table «evo_cron__log»
Creating default blacklist entries... OK.
Creating default groups... OK.
Creating default Post Types... OK.
Creating default file types... OK.
Giving Administrator Group edit perms on files... OK.
Giving Administrator Group full perms on media for all blogs... OK.
Creating default blogs... OK.
Creating sample categories... OK.
Creating default users... OK.
Creating sample posts for blog A... OK.
Creating default linkblog entries... OK.
Creating sample posts... OK.
Creating sample comments... OK.
Creating default group/blog permissions... OK.
Creating default settings... OK.
Installing default plugins...

2 Dec 15, 2007 08:26

Upload all the files to the server again and run the installer. If the problem persists please report back to this topic.

Good luck

3 Dec 15, 2007 17:46

I failed to mention, the version is Key West 1.10.3. I uploaded the directory as "/blogs" and did not change any permissions before attempting to install.

I deleted and reinstalled the database and blogs directory. I attempted to install again and received the same lock up.

4 Dec 15, 2007 18:10

Can you visit your server to see how much of the plugins folder got installed? I'm not sure why, but it MIGHT help understand why installation is hanging at that particular point.

Also when you tried the second time did you start from a brand new download of the package? My thought there is "what if something got messed up when downloading and unzipping?" IF that is the case then a brand new download and unzip would get rid of the issue.

5 Dec 15, 2007 18:38

I will try downloading the file again.

Also...where do I look on the server to see how far the installation got?

6 Dec 15, 2007 19:08

I downloaded again, reinstalled and get the same problem.

7 Dec 15, 2007 19:09

This is what is currently showing in the database.

b2evolutionblogs (31)
evo_antispam
evo_basedomains
evo_bloggroups
evo_blogs
evo_blogusers
evo_categories
evo_coll_settings
evo_comments
evo_cron (2)
evo_cron__log
evo_cron__task
evo_files
evo_filetypes
evo_groups
evo_hitlog
evo_item (1)
evo_item__prerendering
evo_links
evo_locales
evo_pluginevents
evo_plugins
evo_pluginsettings
evo_pluginusersettings
evo_postcats
evo_posts
evo_poststatuses
evo_posttypes
evo_sessions
evo_settings
evo_subscriptions
evo_useragents
evo_users
evo_usersettings

8 Dec 15, 2007 19:13

try increasing your memory limit in conf/advanced.php

// To help debugging severe errors, you'll probably want PHP to display the errors on screen.
// In this case, uncomment the following line:
//ini_set( 'display_errors', 'on' );
// If you get blank pages, PHP may be crashing because it doesn't have enough memory.
// The default is 8 MB (set in php.ini)
// Try uncommmenting the following line:
ini_set( 'memory_limit', '16M' );

¥

9 Dec 15, 2007 20:38

I made this 64M instead of 16M and it still stops at installing the default plug-ins.

10 Dec 15, 2007 20:46

make a new file called phpinfo.php and put in it:

<?php
phpinfo()
?>


upload it to your server and call it in a webbrowser like yoursite.com/phpinfo.php. It will spit out a lot of information, one of the items being the max excecutable size or something siilar.
Please report back to this topic. You can also provide a link to this phpinfo file.

Good luck

12 Dec 15, 2007 22:22

memory_limit 12M

Did you ever set it to 12Mb? You wrote you set it to 64Mb. Never mind. This shows your host doesn't allow you to change the memory setting through php_ini.

Then again, 12Mb should be enough, at least for the installation process.
Does cPanel have an option to switch to php5? If so, try that.

13 Dec 15, 2007 22:45

I have changed it to php5 and it still gets to the same location on the install and stops. Frustrating!!

14 Dec 15, 2007 23:16

The database install seems to be OK, so let's try to get into the blog. Type into URL box of your browser: YOURDOMAIN.xxx/blogs/index,php (or wherever you have your blog situated).

16 Dec 16, 2007 00:44

With Yabba and Afwas on the case all I can do is add a bit of noise, but so what: noise is FUN!

You can use your host's file manager or your FTP program to see the file directory on your server. It might offer a clue as to what's happening, although now that I think of it all the files are probably there.

Using phpmyadmin, can you see what - if anything - is in your plugins table?

Another thing you could consider trying is to edit your install/_functions_install.php file and comment out the actual plugin installation. IF it gets you past the hang point then we can proceed to maybe figure out WHY it won't let you past that point during installation. In that file around line 254 you will see quite a few lines like this:

$Plugins_admin->install( 'quicktags_plugin' );

Comment them out by putting // in front of them, like this:

//$Plugins_admin->install( 'quicktags_plugin' );

This MIGHT allow the installer to continue. If so then you can install the plugins via the back office, or find out what causes the problem when you try to install plugins via the back office.

But I'm sure Afwas and Yabba will have better methods to address this problem. They're smart. They know stuff about stuff.

17 Dec 16, 2007 01:05

I can't locate that in the file. There are only 124 lines in the conf/_functions_install.php.

18 Dec 16, 2007 01:05

Here is the conf/_funcions_install.php:

<?php
/**
 * This file implements support functions for the installer
 *
 * b2evolution - {@link http://b2evolution.net/}
 * Released under GNU GPL License - {@link http://b2evolution.net/about/license.html}
 * @copyright (c)2003-2007 by Francois PLANQUE - {@link http://fplanque.net/}
 *
 * @package install
 */
if( !defined('EVO_MAIN_INIT') ) die( 'Please, do not access this page directly.' );

/**
 * check_db_version(-)
 *
 * Note: version number 8000 once meant 0.8.00.0, but I decided to switch to sequential
 * increments of 10 (in case we ever need to introduce intermediate versions for intermediate
 * bug fixes...)
 */
function check_db_version()
{
	global $DB, $old_db_version, $new_db_version;

	echo '<p>'.T_('Checking DB schema version...').' ';

	if( db_col_exists( 'T_settings', 'set_name' ) )
	{ // we have new table format (since 0.9)
		$old_db_version = $DB->get_var( 'SELECT set_value FROM T_settings WHERE set_name = "db_version"' );
	}
	else
	{
		$old_db_version = $DB->get_var( 'SELECT db_version FROM T_settings' );
	}

	if( empty($old_db_version) ) debug_die( T_('NOT FOUND! This is not a b2evolution database.') );

	echo $old_db_version, ' : ';

	if( $old_db_version < 8000 ) debug_die( T_('This version is too old!') );
	if( $old_db_version > $new_db_version ) debug_die( T_('This version is too recent! We cannot downgrade to it!') );
	echo "OK.<br />\n";
}


/**
 * Clean up extra quotes in posts
 */
function cleanup_post_quotes( $col_ID = 'ID' )
{
  global $DB;

	echo "Checking for extra quote escaping in posts... ";
	$query = "SELECT $col_ID, post_title, post_content
							FROM T_posts
						 WHERE post_title LIKE '%\\\\\\\\\'%'
						 		OR post_title LIKE '%\\\\\\\\\"%'
						 		OR post_content LIKE '%\\\\\\\\\'%'
						 		OR post_content LIKE '%\\\\\\\\\"%' ";
	/* FP: the above looks overkill, but MySQL is really full of surprises...
					tested on 4.0.14-nt */
	// echo $query;
	$rows = $DB->get_results( $query, ARRAY_A );
	if( $DB->num_rows )
	{
		echo 'Updating '.$DB->num_rows.' posts... ';
		foreach( $rows as $row )
		{
			// echo '<br />'.$row['post_title'];
			$query = "UPDATE T_posts
								SET post_title = ".$DB->quote( stripslashes( $row['post_title'] ) ).",
										post_content = ".$DB->quote( stripslashes( $row['post_content'] ) )."
								WHERE $col_ID = ".$row[$col_ID];
			// echo '<br />'.$query;
			$DB->query( $query );
		}
	}
	echo "OK.<br />\n";

}

/**
 * Clean up extra quotes in comments
 */
function cleanup_comment_quotes()
{
  global $DB;

	echo "Checking for extra quote escaping in comments... ";
	$query = "SELECT comment_ID, comment_content
							FROM T_comments
						 WHERE comment_content LIKE '%\\\\\\\\\'%'
						 		OR comment_content LIKE '%\\\\\\\\\"%' ";
	/* FP: the above looks overkill, but MySQL is really full of surprises...
					tested on 4.0.14-nt */
	// echo $query;
	$rows = $DB->get_results( $query, ARRAY_A );
	if( $DB->num_rows )
	{
		echo 'Updating '.$DB->num_rows.' comments... ';
		foreach( $rows as $row )
		{
			$query = "UPDATE T_comments
								SET comment_content = ".$DB->quote( stripslashes( $row['comment_content'] ) )."
								WHERE comment_ID = ".$row['comment_ID'];
			// echo '<br />'.$query;
			$DB->query( $query );
		}
	}
	echo "OK.<br />\n";

}


/**
 * Validate install requirements.
 *
 * @return array List of errors, empty array if ok.
 */
function install_validate_requirements()
{
	$errors = array();

	return $errors;
}



?>



*edit*
PHP code in a box looks much nicer

19 Dec 16, 2007 01:06

My mistake...I meant to say the install...not conf folder.

20 Dec 16, 2007 01:27

The same conf/advanced.php, change $debug to 2, display your errors and play with your memory :

/**
 * Display debugging informations?
 *
 * 0 = no
 * 1 = yes
 * 2 = yes and potentially die() to display debug info (needed before redirects, e-g message_send.php)
 *
 * @global integer
 */
$debug = 2;

// Most of the time you'll want to see all errors, including notices:
// b2evo should run notice free! (plugins too!)
error_reporting( E_ALL );

// To help debugging severe errors, you'll probably want PHP to display the errors on screen.
// In this case, uncomment the following line:
ini_set( 'display_errors', 'on' );
// If you get blank pages, PHP may be crashing because it doesn't have enough memory.
// The default is 8 MB (set in php.ini)
// Try uncommmenting the following line:
ini_set( 'memory_limit', '112M' );// weirdly, it may be worth setting this to 0 and seeing if it works

¥

21 Dec 16, 2007 01:53

I set the debug to 2, but get no errors when it freezes on the default plugins.

I also tried changing the memory to '0'. This did not help either.

In case in helps and anyone has had experience with their setup...my host is Startlogic. I have worked with your blogs on the virtual server before, but they were already installed there. This new account is a shared hosting with my own MySQL databases.

22 Dec 16, 2007 17:04

Aw crap my bad. I looked at the files for 2.2.0 so of course yours don't match. How about the actual contents of your evo_plugins table in your database?

We know it gets to the point where it says it is installing default plugins, but we don't know how much further than that it gets. Is it installing plugins then hanging, or hanging when installing plugins?

I'll find the right file and line to reference!

23 Dec 16, 2007 17:43

Here is what I am showing in the evo_plugins table:

evo_plugins
Field Type Null Default
plug_ID int(11) No
plug_priority tinyint(4) No 50
plug_classname varchar(40) No
plug_code varchar(32) Yes NULL
plug_apply_rendering enum('stealth', 'always', 'opt-out', 'opt-in', 'lazy', 'never') No never
plug_version varchar(42) No 0
plug_name varchar(255) Yes NULL
plug_shortdesc varchar(255) Yes NULL
plug_status enum('enabled', 'disabled', 'needs_config', 'broken') No
plug_spam_weight tinyint(3) No 1

Indexes: Keyname Type Cardinality Field
PRIMARY PRIMARY 5 plug_ID
plug_code UNIQUE None plug_code
plug_status INDEX None plug_status

Space usage: Type Usage
Data 240 Bytes
Index 4,096 Bytes
Total 4,336 Bytes
Row Statistics: Statements Value
Format dynamic
Rows 5
Row length ø 48
Row size ø 867 Bytes
Next Autoindex 6
Creation Dec 15, 2007 at 07:44 PM
Last update Dec 15, 2007 at 07:44 PM

24 Dec 16, 2007 18:11

Okay now I'm up to speed. In 1.10.3 the last thing it says to you comes from install/_functions_create.php on line 1022. I was hoping you would browse the table, but knowing it has only five lines gives me some info to work with.

The sixth plugin installed by default is "code_highlight_plugin", and I focus on the sixth because your paste reveals that your plugin table has 5 rows in it.

So try this. FIRST browse the table contents to see if I'm correct in saying you have 5 plugins installed in that table. I do not know exactly what you'll see, but I hope it is fairly straightforward when you get in there. IF you have everything up to "smilies" and to not have "code_highlight_plugin" then you should see if the file and line I identified in this post match your files. IF they match then comment out the code_highlight_plugin plugin and see what you get.

Sorry, but that means wiping the database clean (drop tables) and installing again.

IF IF IF you can get even one line further then we're learning something.

My goal is to learn exactly which line is killing your installation.

I'm sorry this is such a PITA for you, and I'm hopeful that we can find resolution for both you AND the application. It *should* be able to install and work is the thing. Seeing that you can't install 1103 is a bummer.

25 Dec 16, 2007 18:19

My apologies, here is what I get on the browse:

SQL result
Host: custsql-sl02.eigbox.net
Database: rodsblog
Generation Time: Dec 16, 2007 at 12:11 PM
Generated by: phpMyAdmin 2.8.0.1 / MySQL 5.0.45-log
SQL query: SELECT * FROM `evo_plugins` LIMIT 0, 30 ;
Rows: 5

plug_ID plug_priority plug_classname plug_code plug_apply_rendering plug_version plug_name plug_shortdesc plug_status plug_spam_weight
1 30 quicktags_plugin b2evQTag never 1.10 NULL NULL enabled 1
2 70 auto_p_plugin b2WPAutP opt-out 1.9 NULL NULL enabled 1
3 60 autolinks_plugin b2evALnk opt-out 1.9-dev NULL NULL enabled 1
4 90 texturize_plugin b2WPTxrz opt-out 1.9-dev NULL NULL enabled 1
5 15 smilies_plugin b2evSmil opt-out 1.10 NULL NULL enabled 1

I will comment out that line you mentioned though.

26 Dec 16, 2007 18:22

Interesting. It says the installation is successful now!

27 Dec 16, 2007 18:24

The only errors I get after installation are:
Plugin class file [plugins/_.php [DEBUG: /hermes/bosweb06/b2820/sl.rodsrecords/public_html/blogs/plugins/_.php]] is not readable!
Unregistered plugin []!

28 Dec 16, 2007 18:28

Wow I wish the smart people would come back.

Can you delete the ... whatever plugin it was you bypassed from your server and see if you don't get that error? I'm guessing again is the thing, only now I'm guessing that just having that particular plugin is somehow crufting up your blog.

BTW I think it will end up being something 'unusual' about your server config. I have no idea what, but wow 1103 is the end of the line for a version that - to the best of my knowledge - didn't have this problem for any other user.

BTW you should find the file on your server as "/plugins/whatever_it_was.plugin.php".

29 Dec 16, 2007 18:56

I deleted the entire code_highlight_plugin plugin line in the install/_functions_creste.php file and do not get any errors on install now.

Were these plugins necessary for the blog to work correctly, however?

30 Dec 16, 2007 19:00

Actually, I tried to get to the admin page now and it does not work. Even though I already have b2evolution pre-installed in my virtual server. I am going to try installing from scratch there also...just to see if it works or not.

31 Dec 16, 2007 19:52

I just tried to install this on a virtual hosting account and the install freezes at exactly the same point.

There is a version of b2evolution that was installed by my host on this virtual server that functions just fine. It is a really old version though: 0.9.0.12. (As I stated, I did not install this from scratch though).

32 Dec 16, 2007 21:28

Can you, just for the sake of it, install 1.9.3 on either of the hosts that don't work.

Reading your story and particularly the part where you remove the Highlight plugin, tells me this is probably a memory related issue after all. Can you persuade your host to tap that to 16Mb?

You can try installing WAMP on your compu. That's a quick job. You then can install 1.10.3 on your desktop and see if it runs. Both my first and this last suggestion are for you to see what happens if it works :>

Good luck

33 Dec 16, 2007 22:23

So that I can ask my host exactly what I need, is this a MYSQL database memory problem?

I will download the 1.9.3 and try that.

34 Dec 16, 2007 22:29

jeskremer wrote:

So that I can ask my host exactly what I need, is this a MYSQL database memory problem?

I will download the 1.9.3 and try that.

No, a PHP memory issue. They need to put

 memory_limit = 16M


In their php.ini

Good luck

35 Dec 17, 2007 00:06

The b2evolution 1.9.3 installed just fine. I guess I might just use this. I looked at the php.ini file for php 5. I am not an expert at php, but it states here:

memory_limit = 18M ; Maximum amount of memory a script may consume (8MB)

36 Dec 17, 2007 00:08

Should I change this in the php.ini file:

Maximum size of POST data that PHP will accept.
post_max_size = 8M

37 Dec 17, 2007 00:28

jeskremer wrote:

I deleted the entire code_highlight_plugin plugin line in the install/_functions_creste.php file and do not get any errors on install now.

Hmmm, weird, I wonder why the code highlighter tripped the memory limit, it should have the smallest footprint out there .... another headache to add to my list.

You only need to alter the memory limit, not the post max size

¥

38 Dec 17, 2007 00:34

OK. I changed the post_max_size=8M to 16M in the php.ini file. I have reinstalled the latest stable release of the b2evolution again and get this at the bottom of the install page:

Parse error: syntax error, unexpected '%' in /hermes/bosweb06/b2820/sl.rodsrecords/public_html/blogs/plugins/code_highlight_plugin/_code_highlight.plugin.php on line 377

39 Dec 17, 2007 00:39

ok, now that is weird, because this is the section of code from that area ( 363 -> 386 )

	/**
	 * Spits out the styles used
	 *
	 * @see Plugin::SkinBeginHtmlHead()
	 */
	function SkinBeginHtmlHead()
	{
		 echo '<style type="text/css">
/* AstonishMe code plugin styles */
.amc0,.amc1,.amc2,.amc3,.amc4,.amc5,.amc6,
.amc7,.amc8,.amc9 { background:
  url('.$this->get_plugin_url().'img/numbers.gif) no-repeat; }
</style>';

		echo '<link rel="stylesheet" type="text/css" href="'.$this->get_plugin_url().'amcode.css" />
<!--[if IE]>
<style type="text/css">
/* IE: make sure the last line is not hidden by a scrollbar */
div.codeblock.amc_short table {
	margin-bottom: 2ex;
}
</style>
<![endif]-->';
	}

Could you possibly download a fresh copy of the zip from the downloads page and upload the fresh /plugins/ folder and try installing again?

¥

*edit*
Just out of curiosity, before you go to all that effort, can you change the first bit of that section of code to :

	/**
	 * Spits out the styles used
	 *
	 * @see Plugin::SkinBeginHtmlHead()
	 */
	function SkinBeginHtmlHead()
	{
		echo $this->get_plugin_url();

do another install and see what it spits out ( and if the error remains, and what line number )
¥

40 Dec 17, 2007 00:53

How much of the original code should I paste this new code over?

41 Dec 17, 2007 00:57

Just add the echo line into the original code at the point I've shown.

I'm just curious to see what it echo's and if the error changes

¥

42 Dec 17, 2007 01:05

1. I downloaded the b2evolution file again and got the same errors.

2. I changed the _code_hightlight_plugin.php to read:

/**
	 * Spits out the styles used
	 *
	 * @see Plugin::SkinBeginHtmlHead()
	 */
	function SkinBeginHtmlHead()
	{
	echo $this->get_plugin_url(); 
		 echo '<style type="text/css">
/* AstonishMe code plugin styles */
.amc0,.amc1,.amc2,.amc3,.amc4,.amc5,.amc6,
.amc7,.amc8,.amc9  { background: url("../../../../../../../Local%20Settings/Temp/.$this-%3eget_plugin_url().") }
</style>';

		echo '<link rel="stylesheet" type="text/css" href="../../../../../../../Local%20Settings/Temp/'.$this-%3eget_plugin_url().'amcode.css" />
<!--[if IE]>
<style type="text/css">
/* IE: make sure the last line is not hidden by a scrollbar */
div.codeblock.amc_short table {
	margin-bottom: 2ex;
}
</style>
<![endif]-->';
	}

I get the same: Parse error: syntax error, unexpected '%' in /hermes/bosweb06/b2820/sl.rodsrecords/public_html/blogs/plugins/code_highlight_plugin/_code_highlight.plugin.php on line 377

43 Dec 17, 2007 01:05

I guess I screwed up the format of that last post.

44 Dec 17, 2007 01:08

lol, don't worry about the format I can fix that.

Tad confused how you managed to get the same error on the same line when you added a line above the original code ( so either way the error should have moved )

..... wanders off to think ....

¥
*edit*
urm, your code shows some differences to what's in the file :

/* AstonishMe code plugin styles */
.amc0,.amc1,.amc2,.amc3,.amc4,.amc5,.amc6,
.amc7,.amc8,.amc9 { background: url("../../../../../../../Local%20Settings/Temp/.$this-%3eget_plugin_url().") }
</style>';

echo '<link rel="stylesheet" type="text/css" href="../../../../../../../Local%20Settings/Temp/'.$this-%3eget_plugin_url().'amcode.css" />
<!--[if IE]>

45 Dec 17, 2007 01:17

I'll get to this in about an hour...time to frost cookies with the kids.

46 Dec 17, 2007 01:21

I'll be asleep by then ;)

¥

47 Dec 17, 2007 02:54

I don't know why I got that extra stuff in the code. I recopied the file, entered the snippet of code on line 377 that you told me to add, attempted to reinstall and got the error on line 378:

Parse error: syntax error, unexpected '%' in /hermes/bosweb06/b2820/sl.rodsrecords/public_html/blogs/plugins/code_highlight_plugin/_code_highlight.plugin.php on line 378

Here is what the _code_highlight_plugin.php looks like now:

/**
	 * Spits out the styles used
	 *
	 * @see Plugin::SkinBeginHtmlHead()
	 */
	function SkinBeginHtmlHead()
	{
		 echo $this->get_plugin_url();
		 echo '<style type="text/css">
/* AstonishMe code plugin styles */
.amc0,.amc1,.amc2,.amc3,.amc4,.amc5,.amc6,
.amc7,.amc8,.amc9 { background:
  url(.$this-%3eget_plugin_url().img/numbers.gif) no-repeat; }
</style>';

		echo '<link rel="stylesheet" type="text/css" href="'.$this-%3eget_plugin_url().'amcode.css" />
<!--[if IE]>
<style type="text/css">
/* IE: make sure the last line is not hidden by a scrollbar */
div.codeblock.amc_short table {
	margin-bottom: 2ex;
}
</style>
<![endif]-->';
	}

48 Dec 17, 2007 03:16

url(.$this-%3eget_plugin_url().img/numbers.gif) no-repeat; }
</style>';

echo '<link rel="stylesheet" type="text/css" href="'.$this-%3eget_plugin_url().'amcode.css" />

it's still there ;)

¥

49 Jan 10, 2008 02:35

And not...

I wanted to update you folks on the fact that I just tried to reinstall this again. (My frustration period of three weeks was over) and got it to install on the shared server. I was amazed.

I immediately began to install it on my Plesk VPS account and got the same error on install...how strange. It still freezes on:

Creating default settings... OK.
Installing default plugins...

Does anyone know how I can install this manually into MySQL or have any more suggestions. I would really like to use the newest version which is much better than the 0.9.0

50 Jan 10, 2008 11:13

I just installed this from scratch and everything worked fine. It is just the newer versions that don't seem to go.

51 Jan 31, 2008 20:36

Hi!

I'm a totally newbie, but it may be usefull to all:
I have had almost the same problem: after total deleting of b2 and mySQL any attempt to reinstall was finished at 13-th table. Another sequential 2 runs of the installer follow installing another 4 tables (2x2). And nothing more.
The problem was gone when I changed "max_execution_time" from 30 for 600 in php.ini

Sorry for my English


Form is loading...