Messages

16

Older versions / Re: bug with this forum

« on: July 21, 2009, 05:59:10 pm »

Thanks for suggestion.

I had found this similar topic in spanish language...

And this in english

And many bugs with result "upgrade to 1.1.10" 

The error is automatic when logon. I believe that is a problem with the themes or idiom.

One note: an old bug for me was that the forum changed my default keyboard from "español tradicional" to "variante del español". That seems not change now.

Waiting for the forum administrator... 

17

Older versions / Re: bug with this forum

« on: July 20, 2009, 11:03:44 am »

tested from:

4 programs (firefox, opera, chrome, explorer)
3 computers (laptops toshiba and dell, and my personal computer "my hands assembly")
2 differente networks (home and work)
1 person: I believe that my personal profile has some type of problem.

another idea?

18

Older versions / Re: [1.5RC] DB-Upgrade fails: "specified key was too long..."

« on: July 20, 2009, 06:47:08 am »

Solved in the last three messages on this post

and mark as solved in 1.5 beta 3

Code: [Select]

    Changelog
=========
Since 1.5-beta3
---------------
        ...
- bugfix: MySQL Error: Primary key too long.
        ...

what happens?

19

Older versions / Re: bug with this forum

« on: July 16, 2009, 01:00:45 pm »

Tested with Opera, Firefox, Chrome & Internet Explorer.

All is ok if not login   .

When I get login, sometimes is correct and somtimes objects are missing: buttons for reply, icons, ...

This happens only from 1 month ago (more or less). Before all was ok.

20

Español / Re: para que utilizo un backup?

« on: July 16, 2009, 12:30:33 pm »

Bien. al menos he encontrado el fichero db.sql, pero esta vacio.

Ahora al menos cobra sentido, porque es cierto que tengo una copia del sitio que incluye una copia tambien de la base de datos. Y en principio es mas rápido que hacerlo manualmente por ftp.

Otra cosa es que el backup no parece funcionar a dia de hoy (1.4.2), pero para eso ya hay otros hilos abiertos.

En cualquier  caso agradecería que alguien confirmara que es lo correcto:
1.- hay opción para restaurar desde el sistema? (no la veo) 
2.- se produce la restauración automáticamente al poner el zip en la carpeta "tmp/backup"? 
3.- la restauración se hace de modo manual desde el fichero de backup? (que no es poca ventaja) 

Y si contesta un administrador, creo que incluso debe cerrar el hilo.

21

Older versions / bug with this forum

« on: July 13, 2009, 07:48:54 pm »

I have a problem with this forum...

When this text is at the bottom of page, no buttons (post, reply,...) appear. Is imposible send a message or a post, and preview not works.

Code: [Select]

Sorry, the copyright must be in the template.
Please notify this forum's administrator that this site is missing the copyright message for SMF so they can rectify the situation. Display of copyright is a legal requirement. For more information on this please visit the Simple Machines website.

22

Older versions / Re: 1.5 beta 'failed to import database construction'

« on: July 13, 2009, 07:27:30 pm »

ok, solved with this for an upgrade.

For a new instalation I had modified the file public/install/installation/templates/sql/mysql_schema.php with good result too.

Thanks

23

Older versions / Re: 1.5 beta 'failed to import database construction'

« on: July 13, 2009, 06:18:13 pm »

Firt of all: I´m not a progammer (my experience is only with basic:
      zx spectrum basic
      quick basic 4.5
      visual basic

If i understand correctly, this part of  '1_5_figazza.php' creates a key too long

Code: [Select]

CREATE TABLE IF NOT EXISTS `<?php echo $table_prefix ?>template_object_properties` (
`template_id` INT( 10 ) NOT NULL ,
`object_id` INT( 10 ) NOT NULL ,
`object_manager` varchar(255) NOT NULL,
`property` VARCHAR( 255 ) NOT NULL ,
`value` TEXT NOT NULL ,
PRIMARY KEY ( `template_id` , `object_id` ,`object_manager`, `property` )
) ENGINE=<?php echo $engine ?> <?php echo $default_charset ?>;
If it is no correct, please, remove the message...

24

Older versions / Re: 1.5 beta 'failed to import database construction'

« on: July 13, 2009, 05:54:17 am »

Hey boys...

I believe that here is the problem:

http://bugs.mysql.com/bug.php?id=4541

Maybe I'm doing something wrong with my backup, but what is the problem with a new installation?

Sure that is a little problem for you...

25

Older versions / 1.5.beta3 with problems Re: 1.5 beta 'failed to import database construction'

« on: July 12, 2009, 05:45:17 pm »

Now, I have this problem upgrading too.

With version 1.5.beta1 I had upgraded with a few problems but no this.

Now, this is the result for upgrading 1.4.1 to 1.5.beta3

Code: [Select]

Config file found and loaded.
File '/config/config.php' exists and is writable
Folder '/config' exists and is writable
Folder '/public/files' exists and is writable
Folder '/cache' exists and is writable
Folder '/tmp' exists and is writable
Folder '/upload' exists and is writable
Extension 'mysql' is loaded
Extension 'gd' is loaded
Extension 'simplexml' is loaded
Upgrade script has connected to the database.
Test query has been executed. Its safe to proceed with database migration.
Upgrade script has connected to the database.
Test query has been executed. Its safe to proceed with database migration.
Database schema transformations executed (total queries: 2)
OpenGoo has been upgraded. You are now running OpenGoo 1.4.2 Enjoy!
Upgrade script has connected to the database.
Test query has been executed. Its safe to proceed with database migration.
Failed to execute DB schema transformations. MySQL said: Declaracion de clave demasiado larga. La maxima longitud de clave es 1000
Error upgrading to version 1.5-beta3

26

Older versions / Re: 1.5 beta 'failed to import database construction'

« on: July 10, 2009, 07:56:15 pm »

In this check, this is the new error...

Code: [Select]

Step 4: Finish

Installation process:
Database connection has been established successfully
Failed to import database construction. MySQL said: Algo est� equivocado en su sintax cerca ') ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci' en la linea 31

and in this case, selecting Innodb has the same result.

All this is with a new installation. In the same server, I had checked an upgrade from 1.4.1 (running fine) to 1.5. With a few problems, finally works ok.

My pack is EasyPHP 2.1 (apache 2.2.3+php 5.2.0+mysql 5.0.27) without changes
Today I had checked with the recent pack EasyPhp 3.0 (apache 2.2.11+php 5.2.8+mysql 5.1.30) without changes and with the same results
EasyPHP makes Opengoo totally portable in a USB stick: is a great and simple choice for tests!!

27

Older versions / Re: 1.5 beta error upgrading from 1.4.1

« on: July 10, 2009, 09:45:27 am »

Great, solved with this line.

Thanks

28

Older versions / Re: 1.5 beta 'failed to import database construction'

« on: July 10, 2009, 09:38:54 am »

Test with your instructions without result.

Is a problem with MyIsam access… I had checked with InnoDB delect and works fine.

Note that I am working over the “Easy PHP” package, perhaps it has a “little” configuration…

29

Older versions / Re: 1.5 beta error upgrading from 1.4.1

« on: July 09, 2009, 03:42:50 pm »

Line changed but without exit. You can see the error in both screens attached and more stuff that probably informs you.

In the message that appears "all" is translate as "öszzes", as you can see.

I suppose that you prefer that I continue test the upgrade from 1.4.1...

30

Older versions / Re: 1.5 beta error upgrading from 1.4.1

« on: July 08, 2009, 03:03:50 pm »

Great! solved this part but...

the first error is now present:

"Notice: Uninitialized string offset: -1 in E:\parawebphp\opengoo\environment\functions\general.php on line 453"

Additionally "missing lang.js" is present