Failed opening required '\httpdocs\administrator/components/com_route66/lib/seoanalyzer.php' (include_path='.;.\includes;.\pear')

Hi Manny,

Thank you for the detailed report.

Those files (lib/plugin.php and lib/seoanalyzer.php) are no longer part of Route 66 v2.x, so this error usually means something is still trying to load files from an old version.

The most common causes are:

1. Leftover files from a previous version. The upgrade process normally removes deprecated files, but in some cases this may fail (e.g. interrupted update or file permission issues).
2. PHP OPcache. OPcache may still be referencing old file paths.
3. Third-party extension or custom code. Another extension or override may still be trying to include those old Route 66 files.

What to try first

1. Keep the Route 66 system plugin disabled (as you already did).
2. Clear OPcache (restart PHP / web server).
3. Reinstall Route 66 v2.3.1 over the existing installation (no uninstall needed).
4. Re-enable the Route 66 system plugin.

If the issue persists after that, please open a new private ticket and include:

• Administrator login credentials
• FTP (or file manager) access

I’ll take a look directly and clean up any remaining leftovers for you.

Best regards,
Lefteris

Hi Manny,

I’ve resolved the issue on your site.

It was caused by leftover files/extensions from Route 66 v1.11.1 that were still being referenced after the upgrade.

I can’t say with certainty why the cleanup failed during the update (this can happen due to file permissions, interrupted updates, or server-level restrictions), but we’ll be updating Route 66 so that all deprecated extensions are explicitly disabled before removal, to prevent this from happening again in future upgrades.

Upgrading another site from v1.x → v2.3.1

If you plan to upgrade another site from the 1.x series, I strongly recommend the following steps before installing v2.3.1:

1. Go to System → Manage Extensions
2. Search for “route” to list all Route 66 extensions
3. Disable all Route 66 extensions
4. Install Route 66 v2.3.1

Alternatively, you can wait for the next Route 66 update, which will handle this process automatically during the upgrade.

If you need any help with the second site as well, feel free to reach out.

Best regards,
Lefteris

Hi Manny,

Thanks for the detailed update, that helps a lot.

Database version warning

The database warning is probably caused by leftover Route 66 extensions from the 1.x series.

Even if they are disabled, they are still installed and Joomla keeps their old manifest data.

You can safely:

1. Go to System → Manage Extensions
2. Search for “route”
3. Uninstall any Route 66 extensions that still show a 1.x version
4. Keep only the Route 66 extensions that belong to v2.3.1

After that, the database warning should be gone.

Crawler detecting only 5 pages

This is not a timing issue.

The crawler is correctly indexing only the pages that are accessible on the frontend.

Since the pages are returning 404 errors, Route 66 stops there — that’s expected behavior.

Frontend 404 errors (root cause)

In Route 66 v2.x, the URL Patterns settings were moved:

They are no longer in the plugins
They are now in Components → Route 66 → Options

Normally these settings are migrated automatically during the upgrade, but since the upgrade initially failed, that migration likely did not complete.

Additionally, since you manually updated plugin records in the database, it’s very possible that some plugin settings were changed or reset in the process.

If you don’t remember the exact configuration, it would be best to check a backup of the site and compare the previous Route 66 settings.

What to do now:

1. Go to Components → Route 66 → Options
2. Reconfigure your URL Patterns / routing settings
3. Save the options
4. Clear Joomla cache
5. Run crawl again

Once the frontend URLs resolve correctly, the crawler will start detecting all articles normally.

If you’d like, I can log in directly and configure this for you to make sure everything matches your previous setup. Just let me know and I’ll take care of it.

Best regards,
Lefteris

Hi Manny,

I’ve updated the URL patterns under the Route 66 component options, and the frontend links are now working correctly.

For reference, I set the article URL pattern to:

{articleAlias}

Since everything is working as expected now, this is the pattern you should continue using going forward (and in future versions as well).

If you notice anything else behaving unexpectedly, just let me know.

Best regards,
Lefteris

Hi Manny,

Glad to hear everything is working fine now.

There is no hard limit in Route 66 PRO on the number of pages that can be crawled, so the 1,600 pages you’re seeing is not a restriction.

What usually happens in cases like this is one (or a combination) of the following:

• Some pages are not reachable via internal links (orphans), so the crawler can’t discover them
• Pages are excluded by menu structure, access level, language, or publication status
• Pages return non-200 responses (404, redirects, noindex, unpublished, etc.)
• Pagination or category layouts limit how deep articles are linked internally

Route 66 crawls by discovering links, not by reading the database directly, so it can only index pages that are actually accessible from the site structure.

What you can do

Check whether the missing articles:

• are unpublished
• belong to categories not linked in menus
• have access levels other than Public

If you want, you can tell me:

• which content type is missing (articles, categories, tags, etc.)
• whether those articles are linked through menus or category layouts

Best regards,
Lefteris

Hi Manny,

This is not related to languages, categories, or Route 66 limits.

Route 66 crawls only pages that are reachable via frontend links.

It does not scan the database.

The pages that are missing from the crawl are simply not linked anywhere on your site. Because of that, the crawler cannot discover them.

If you believe those pages are linked, please send one example URL of an article that:

• exists,
• is published,
• and is reachable via normal site navigation,

and I’ll check it immediately.

Once a page is linked somewhere on the frontend, Route 66 will pick it up automatically.

Best regards,
Lefteris

Hi Manny,

I’ve checked the URL you provided, and it has already been crawled.

You can see it here in Route 66:

https://astrogradual.com/administrator/index.php?option=com_route66&task=page.edit&id=721

So Route 66 is working correctly in this case.

Just to clarify one important point again:

having a page published is not enough for a crawler.

Route 66 only crawls links that it can discover by navigating the site, exactly like search engines do. This means:

• a page must be linked from another page
• and that page must also be linked
• and so on, starting from an entry point (usually the homepage or menu links)

For example, even if:

• a category is published, and
• all its articles are published,

…if there are no menu links or frontend paths leading to that category or its articles, the crawler cannot discover them.

This is why the total number of crawled pages depends on site structure and internal linking, not on how many articles exist in the backend.

If you believe there are still articles that are:

• published,
• reachable via normal site navigation,
• and missing from the crawl,

please send one example URL and I’ll check it immediately.

Best regards,
Lefteris

Hi Manny,

Just to clarify one last thing for the record:

Whether Google has crawled or indexed a page is not related to Route 66 here.

Route 66 only reflects what it can discover through your site’s internal links. If there is a page that:

• is published,
• is reachable through normal site navigation,
• and still does not appear in the Route 66 crawled pages list,

then that would indicate a real issue worth investigating.

If you come across such a case, just send one example URL and I’ll happily take another look.

Feel free to close the ticket for now, and you’re always welcome to reach out if anything else comes up.

Best regards,
Lefteris