Out of range value for column

Hi,

We are getting issues with edocman:

When trying to save a category:
Out of range value for column 'lft' at row 87

When trying to run "rebuild categories" An error has occurred.

1264 Out of range value for column 'lft' at row 87

What could this be? is it limits on columns within mysql?

Thank you

This is a lof from everything.php

error Uncaught Throwable of type Joomla\Database\Exception\ExecutionFailureException thrown with message "Out of range value for column 'lft' at row 87". Stack trace: #0 [ROOT]\libraries\vendor\joomla\database\src\DatabaseDriver.php(651): Joomla\Database\Mysqli\MysqliStatement->execute()
#1 [ROOT]\libraries\src\Table\Nested.php(1681): Joomla\Database\DatabaseDriver->execute()
#2 [ROOT]\libraries\src\Table\Nested.php(371): Joomla\CMS\Table\Nested->_runQuery()
#3 [ROOT]\libraries\src\Table\Nested.php(803): Joomla\CMS\Table\Nested->moveByReference()
#4 [ROOT]\libraries\src\Table\Table.php(929): Joomla\CMS\Table\Nested->store()
#5 [ROOT]\administrator\components\com_edocman\controller\controller.php(184): Joomla\CMS\Table\Table->store()
#6 [ROOT]\administrator\components\com_edocman\libraries\rad\controller\controller.php(306): EDocmanController->rebuild_documents()
#7 [ROOT]\administrator\components\com_edocman\edocman.php(47): OSController->execute()
#8 [ROOT]\libraries\src\Dispatcher\LegacyComponentDispatcher.php(71): require_once('...')
#9 [ROOT]\libraries\src\Dispatcher\LegacyComponentDispatcher.php(73): Joomla\CMS\Dispatcher\LegacyComponentDispatcher::Joomla\CMS\Dispatcher\{closure}()
#10 [ROOT]\libraries\src\Component\ComponentHelper.php(361): Joomla\CMS\Dispatcher\LegacyComponentDispatcher->dispatch()
#11 [ROOT]\libraries\src\Application\AdministratorApplication.php(150): Joomla\CMS\Component\ComponentHelper::renderComponent()
#12 [ROOT]\libraries\src\Application\AdministratorApplication.php(195): Joomla\CMS\Application\AdministratorApplication->dispatch()
#13 [ROOT]\libraries\src\Application\CMSApplication.php(306): Joomla\CMS\Application\AdministratorApplication->doExecute()
#14 [ROOT]\administrator\includes\app.php(58): Joomla\CMS\Application\CMSApplication->execute()
#15 [ROOT]\administrator\index.php(32): require_once('...')
#16 {main}

Hi Richard,
I would like to explain the error you encountered:
"1264 Out of range value for column 'lft' at row 87"
This error occurs because the value being inserted into the 'lft' column in your Joomla assets table exceeds the maximum value allowed by the current data type of that column. This is usually caused by a large number of assets or by certain operations that increase the value of 'lft' beyond its limit.

How to fix this:
To resolve this issue, I recommend using phpMyAdmin to change the attribute of the 'lft' column from its current type (likely INT) to MEDIUMINT. This will allow the column to store larger values and prevent the error from happening again.

Steps to change the column type in phpMyAdmin:
- Open phpMyAdmin and select your Joomla database.
- Find and open the table named #__assets (replace #__ with your actual table prefix).
- Click on the "Structure" tab.
- Locate the 'lft' column and click on "Change" or "Edit".
- Set the column type to MEDIUMINT.
- Save the changes.

After making this adjustment, the error should be resolved.
Thanks
Dam

Hi Dam,

thank you for the reply!

I could not change to MEDIUMINT it gave the same error.

I managed to change the column for lft to BIGINT and then it gave a error for rgt. So I have changed both to BIGINT. Is this correct?

The lowest value is '-18115359518' and the highest is '1689024248199'

I still get weird errors in the site. I have tried saving the category and it give a blank error message like this:"Save failed with the following error: "

I have tried rebuild documents but I get this after five minutes:

In everything.php:

"error    Uncaught Throwable of type Joomla\Database\Exception\ExecutionFailureException thrown with message "BIGINT value is out of range in '(`llp`.`llp_assets`.`lft` - -(4745447499826814046))'". Stack trace: #0 [ROOT]\libraries\vendor\joomla\database\src\DatabaseDriver.php(651): Joomla\Database\Mysqli\MysqliStatement->execute()
#1 [ROOT]\libraries\src\Table\Nested.php(1681): Joomla\Database\DatabaseDriver->execute()
#2 [ROOT]\libraries\src\Table\Nested.php(371): Joomla\CMS\Table\Nested->_runQuery()
#3 [ROOT]\libraries\src\Table\Nested.php(803): Joomla\CMS\Table\Nested->moveByReference()
#4 [ROOT]\libraries\src\Table\Table.php(929): Joomla\CMS\Table\Nested->store()
#5 [ROOT]\administrator\components\com_edocman\controller\controller.php(184): Joomla\CMS\Table\Table->store()
#6 [ROOT]\administrator\components\com_edocman\libraries\rad\controller\controller.php(306): EDocmanController->rebuild_documents()
#7 [ROOT]\administrator\components\com_edocman\edocman.php(47): OSController->execute()
#8 [ROOT]\libraries\src\Dispatcher\LegacyComponentDispatcher.php(71): require_once('...')
#9 [ROOT]\libraries\src\Dispatcher\LegacyComponentDispatcher.php(73): Joomla\CMS\Dispatcher\LegacyComponentDispatcher::Joomla\CMS\Dispatcher\{closure}()
#10 [ROOT]\libraries\src\Component\ComponentHelper.php(361): Joomla\CMS\Dispatcher\LegacyComponentDispatcher->dispatch()
#11 [ROOT]\libraries\src\Application\AdministratorApplication.php(150): Joomla\CMS\Component\ComponentHelper::renderComponent()
#12 [ROOT]\libraries\src\Application\AdministratorApplication.php(195): Joomla\CMS\Application\AdministratorApplication->dispatch()
#13 [ROOT]\libraries\src\Application\CMSApplication.php(306): Joomla\CMS\Application\AdministratorApplication->doExecute()
#14 [ROOT]\administrator\includes\app.php(58): Joomla\CMS\Application\CMSApplication->execute()
#15 [ROOT]\administrator\index.php(32): require_once('...')"

some other errors:

ING 196.182.33.112    assets    No asset found for com_edocman.document.19028, falling back to com_edocman
2025-07-28T14:49:20+00:00      assets    No asset found for com_edocman.document.19028, falling back to com_edocman
2025-07-28T14:49:20+00:00      assets    No asset found for com_edocman.document.19028, falling back to com_edocman
2025-07-28T14:49:20+00:00     assets    No asset found for com_edocman.document.19028, falling back to com_edocman
2025-07-28T14:49:20+00:00      assets    No asset found for com_edocman.document.19028, falling back to com_edocman
2025-07-28T14:49:20+00:00       assets    No asset found for com_edocman.document.19028, falling back to com_edocman
2025-07-28T14:49:20+00:00       assets    No asset found for com_edocman.document.19027, falling back to com_edocman
2025-07-28T14:49:20+00:00      assets    No asset found for com_edocman.document.19027, falling back to com_edocman
2025-07-28T14:49:20+00:00        assets    No asset found for com_edocman.document.19027, falling back to com_edocman
2025-07-28T14:49:20+00:00        assets    No asset found for com_edocman.document.19027, falling back to com_edocman
2025-07-28T14:49:20+00:00       assets    No asset found for com_edocman.document.19027, falling back to com_edocman
2025-07-28T14:49:20+00:00        assets    No asset found for com_edocman.document.19027, falling back to com_edocman
2025-07-28T14:49:21+00:00        assets    No asset found for com_edocman.document.19022, falling back to com_edocman
2025-07-28T14:49:21+00:00       assets    No asset found for com_edocman.document.19022, falling back to com_edocman
2025-07-28T14:49:21+00:00     assets    No asset found for com_edocman.document.19022, falling back to com_edocman

Any other suggestions? 

Yes, you can try to change attribute of column "rgt" to bigint and test it again?
Thanks
Dam

I change both lgt and rgt to bigint before these errors for produced.

Hi Richard,
Thank you for your update and the details regarding the changes to the lft and rgt columns in your Joomla database. The values in your lft and rgt columns are currently extremely large and even negative (e.g., lowest: -18,115,359,518, highest: 1,689,024,248,199). Normally, these columns should contain relatively small positive integers. Such abnormal values indicate that the assets tree structure in your Joomla database has become corrupted, possibly due to an import, a malfunctioning extension, or an incorrect database operation.
In this case, changing the column types to BIGINT does not resolve the root cause and may even create further compatibility issues, as Joomla and its extensions are not designed to handle such large values in these fields.
Unfortunately, your site has many third-party extensions involved, it is extremely difficult—if not impossible—to identify the exact source of the problem or to repair the assets table reliably. Joomla does not have a built-in tool to fully reset or restore the assets tree to a clean state. The assets table is critical for Joomla’s permissions and structure, and once corrupted, it can cause persistent and unpredictable issues throughout your site.
The most practical and safest solution is to restore your site and database from a backup taken before the problem occurred. This will revert the assets table and all related data to a working state.
- Please check if you have a recent backup of your site and database from before these issues started.
- If you do, we strongly recommend restoring from that backup as soon as possible.
- After restoring, consider reviewing and possibly reducing the number of third-party extensions to minimize future risks.
Thanks
Dam