Thread

When upgrading from 2.3.1 to 2.4 I got the following error:

A Database Error Occurred
Error Number: 1146

Table ‘exp_developer_log’ doesn’t exist
SELECT COUNT(*) AS `numrows` FROM (`exp_developer_log`) WHERE `viewed` = ‘n’
Filename: models/tools_model.php
Line Number: 257

I have gotton around this by just creating the table from the mysql schema in the installer, but thought I would flag it.

I noticed this in the changelog

Added the ability to use image manipulations in custom file fields, using both a single tag and a tag pair.

Is there documentation for this somewhere?

I noticed this in the changelog

Added the ability to use image manipulations in custom file fields, using both a single tag and a tag pair.

Is there documentation for this somewhere?

http://ellislab.com/expressionengine/user-guide/modules/channel/custom_fields.html#file-field

When upgrading from 2.3.1 to 2.4 I got the following error:

A Database Error Occurred
Error Number: 1146

Table ‘exp_developer_log’ doesn’t exist
SELECT COUNT(*) AS `numrows` FROM (`exp_developer_log`) WHERE `viewed` = ‘n’
Filename: models/tools_model.php
Line Number: 257

I have gotton around this by just creating the table from the mysql schema in the installer, but thought I would flag it.

Have had the same issue here.

Hi Andru (and Linda & others waiting),

Its obvious that the Gallery import keeps running into issues and pushed back. I am truly sorry about that. And yes, we will keep our support promise if we don’t have a Gallery solution by the time EE 1.x support ends, we’ll continue to provide support for EE 1.x users + Gallery.

Thanks for the update.

One question; the versions of PHP and mySQL that will be required for 2.6, will 1.x run on those? So that its safe to do a preparatory upgrade, I mean.

When upgrading from 2.3.1 to 2.4 I got the following error:

A Database Error Occurred
Error Number: 1146

Table ‘exp_developer_log’ doesn’t exist
SELECT COUNT(*) AS `numrows` FROM (`exp_developer_log`) WHERE `viewed` = ‘n’
Filename: models/tools_model.php
Line Number: 257

I have gotton around this by just creating the table from the mysql schema in the installer, but thought I would flag it.

I have the same Issue. How should the manually generated table look like? I’ve never done this before

- deleted -

When upgrading from 2.3.1 to 2.4 I got the following error:

A Database Error Occurred
Error Number: 1146

Table ‘exp_developer_log’ doesn’t exist
SELECT COUNT(*) AS `numrows` FROM (`exp_developer_log`) WHERE `viewed` = ‘n’
Filename: models/tools_model.php
Line Number: 257

I have gotton around this by just creating the table from the mysql schema in the installer, but thought I would flag it.

Same issue here. I “fixed” the problem by creating a table called exp_developer_log with the following fields:

* id (INT)
* log_id (INT)
* viewed (VARCHAR)
* description (VARCHAR)
* timestamp (TIMESTAMP)

Not ideal, but it worked for now.

When upgrading from 2.3.1 to 2.4 I got the following error:

A Database Error Occurred
Error Number: 1146

Table ‘exp_developer_log’ doesn’t exist
SELECT COUNT(*) AS `numrows` FROM (`exp_developer_log`) WHERE `viewed` = ‘n’
Filename: models/tools_model.php
Line Number: 257

To anyone having this kind of problem. Please check this bug report. In my case, it wasn’t a bug at all but a mistake on my part: running the install wizard with a custom config.php file already specifying the app_version as 240 (2.4)

You can change that value back to 231 (or to the version number you were upgrading from) and re-run the installer. All tables will be created and / or updated.

When upgrading from 2.3.1 to 2.4 I got the following error:

A Database Error Occurred
Error Number: 1146

Table ‘exp_developer_log’ doesn’t exist
SELECT COUNT(*) AS `numrows` FROM (`exp_developer_log`) WHERE `viewed` = ‘n’
Filename: models/tools_model.php
Line Number: 257

To anyone having this kind of problem. Please check this bug report. In my case, it wasn’t a bug at all but a mistake on my part: running the install wizard with a custom config.php file already specifying the app_version as 240 (2.4)

You can change that value back to 231 (or to the version number you were upgrading from) and re-run the installer. All tables will be created and / or updated.

Are you installing this locally? I was able to upgrade a site on my server without a problem but got this hiccup when I installed a local copy.  I think I might start to install a fresh local copy and see how that works.

Thanks for the tip jeromecoupe!  It worked flawlessly for me on my local install.  Saved me a ton of work!

EE 2.4 is working really well for us on the most-part. The EE Reactor change of making fields default to no formatting has been incredibly handy - it’s little things like that which makes me really hopeful for this project.

Any feedback on the stability of this release?  Was about to set up a fresh install for a dev site but I want to make sure there weren’t going to be too many surprises.  We built a bunch of client sites on 2.2.2 and had to deal with a lot of updates.

Looking for feedback on 2.4 as well.

I took this line from the EL blog:
EE 2.5 will ship with a default Editor.
Why i took it? Well im interested if the editor might be available in EE’s Wiki Module also to simplify writing articles to wiki itself. Now you have to “hardcode” everything.

Any response or line from EL Team would be nice to hear, that is the editor in wiki?

Cheers