All add-ons currently require PHP 7.4 or greater.

On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.

Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: Upon upgrading 1.7 to 1.92, BaseTable or View Not Found

Status With Customer
Add-on / Version Speedy 1.92
Severity
EE Version 7.2.6

Paul Larson

May 03, 2024

Could I have some .zip of version between 1.7 and 1.9? Figured I would try smaller steps. Or, does the error provide any clues?

Error attached.

#1

BoldMinded (Brian)

Did you check the database to see if the exp_speedy_diagnostics table was present? Are you positive you clicked the Update button?

#2

BoldMinded (Brian)

If you don’t have the diagnostics table but the version in the exp_modules table is set to 1.9.x then for some reason the updates didn’t run. Providing previous zips files isn’t going to help fix that. You’ll need to update the exp_modules table to 1.8.0 and then click the Update button. Then check to see if the diagnostics table is present.

#3

Paul Larson

Yes, positive I clicked the Update button. The exp_speedy_diagnostics table is not currently present.

Right now my codebase is 1.7.0 (because I simply rolled it back). Though db thinks it is 1.9.2.

Worst case, would I grab the SQL query from upd.speedy.php to create the exp_speedy_diagnostics table if for any other reason it isn’t created?

#4

BoldMinded (Brian)

Don’t manually run the query, change the db so it’s at 1.7.0, drop in the 1.9.x files, then try running the update again.

#5

Paul Larson

I survived this upgrade on second attempt. You may close. Thanks!

#6

Paul Larson

Actually. Don’t close.

The update SEEMED to be ok, until I went to edit an entry, then I got the attached error. (Unknown column. speedy_m_CacheBreaking…)

screenshot:

#7

BoldMinded (Brian)

The screenshot isn’t loading and you truncated the error message.

#8

Paul Larson

The screenshot is there, the preview icon is broken. Right click on the image to go to the url:

https://ucea086526ef78f7e0cc19e149d3.dl.dropboxusercontent.com/cd/0/inline/CSTVV_cBZV_H4Uvbu2zI74gpIAzoZ5hN6Hg3F43l_ZdpLGw2VLqFt7OHvqWyInch9iMnKel5B3Ce6vikQO9aQHtLL_p7u0kJhUqFzK1VK2GFrze_6uoTjxCaXZ8AFRyYBGQ/file

or this:

https://tinyurl.com/bold-minded

#9

BoldMinded (Brian)

both of those are 404’ing :(

#10

Paul Larson

This error occurs when I visit the ‘Cache Clearing’ nav link in the addon.

Exception Caught

SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘speedy_m_CacheBreaking_speedy_breaking.statuses’ in ‘field list’: SELECT speedy_m_CacheBreaking_speedy_breaking.id as speedy_m_CacheBreaking__id, speedy_m_CacheBreaking_speedy_breaking.channel_id as speedy_m_CacheBreaking__channel_id, speedy_m_CacheBreaking_speedy_breaking.refresh as speedy_m_CacheBreaking__refresh, speedy_m_CacheBreaking_speedy_breaking.tags as speedy_m_CacheBreaking__tags, speedy_m_CacheBreaking_speedy_breaking.items as speedy_m_CacheBreaking__items, speedy_m_CacheBreaking_speedy_breaking.statuses as speedy_m_CacheBreaking__statuses, speedy_m_CacheBreaking_speedy_breaking.categories as speedy_m_CacheBreaking__categories FROM (exp_speedy_breaking as speedy_m_CacheBreaking_speedy_breaking) WHERE ( speedy_m_CacheBreaking_speedy_breaking.channel_id = 0 ) LIMIT 1

ee/legacy/database/drivers/mysqli/mysqli_connection.php:114

Stack Trace: Please include when reporting this error

0 ee/legacy/database/drivers/mysqli/mysqli_driver.php(112): CI_DB_mysqli_connection->query()

1 ee/legacy/database/DB_driver.php(260): CI_DB_mysqli_driver->_execute()

2 ee/legacy/database/DB_driver.php(175): CI_DB_driver->simple_query()

3 ee/legacy/database/DB_active_rec.php(1083): CI_DB_driver->query()

4 ee/ExpressionEngine/Service/Model/Query/Select.php(60): CI_DB_active_record->get()

5 ee/ExpressionEngine/Service/Model/DataStore.php(275): ExpressionEngine\Service\Model\Query\Select->run()

6 ee/ExpressionEngine/Service/Model/DataStore.php(220): ExpressionEngine\Service\Model\DataStore->runQuery()

7 ee/ExpressionEngine/Service/Model/Query/Builder.php(150): ExpressionEngine\Service\Model\DataStore->selectQuery()

8 ee/ExpressionEngine/Service/Model/Query/Builder.php(55): ExpressionEngine\Service\Model\Query\Builder->fetch()

9 user/addons/speedy/mcp.speedy.php(377): ExpressionEngine\Service\Model\Query\Builder->first()

10 [internal function]: Speedy_mcp->cache_clearing()

11 ee/ExpressionEngine/Controller/Addons/Addons.php(1577): call_user_func_array()

12 ee/ExpressionEngine/Controller/Addons/Addons.php(857): ExpressionEngine\Controller\Addons\Addons->getModuleSettings()

13 [internal function]: ExpressionEngine\Controller\Addons\Addons->settings()

14 ee/ExpressionEngine/Core/Core.php(268): call_user_func_array()

15 ee/ExpressionEngine/Core/Core.php(124): ExpressionEngine\Core\Core->runController()

16 ee/ExpressionEngine/Boot/boot.php(184): ExpressionEngine\Core\Core->run()

17 httpdocs/admin.php(144): require_once(‘…’)

17 httpdocs/admin.php(144): require_once(‘…’)

#11

BoldMinded (Brian)

I don’t know why you’re having trouble with the upgrades, but this column was added in the 1.8 version, and is added through a pretty typical update file: /speedy/updates/up_1_08_00.php

It seems your updates are not triggering correctly for some reason, which isn’t an issue I’ve had others report.

#12

BoldMinded (Brian)

I assume this issue is resolved?

#13

Paul Larson

Technically it’ still open because I rolled back to 1.7. I’d like to give it one more try: setting the exp_modules version to 1.7 and trying again. (I think I set it to 1.8 last time but in hindsight maybe it should have been 1.7 to re-trigger the update)

Login to reply