Class error not found joomla 4

При обновлении до 4.03 Произошла ошибка Class 'JRequest' not found - Joomla 4.x: [FAQ] Часто задаваемые вопросы и ответы

0 Пользователей и 1 Гость просматривают эту тему.

  • 5 Ответов
  • 2187 Просмотров

Подскажите, как исправить эту ошибку?
0 Class ‘JRequest’ not found

в 4-ке уже нет этого класса. Параметры надо читать через $app->input

в 4-ке уже нет этого класса. Параметры надо читать через $app->input

А где это искать?

А где это искать?

в устаревших расширениях. А еще можете логи на сервере посмотреть — там будет указан файл и строка, в которых вывалилась ошибка.

Включаем отладку в общих настройках и вперёд, искать, какое из расширений выбрасывает ошибку. В ошибке будует виден путь.
Совет — не спешите с переходом на Joomla 4.

Moderator: General Support Moderators

stargazer1682

Joomla! Enthusiast
Joomla! Enthusiast
Posts: 177
Joined: Sat Jan 10, 2009 7:16 am

Migration to Joomla 4 Failed — Class «JRequest» not found

I’m working on migrating a client’s website to Joomla 4, currently running Joomla 3.10.10, PHP 8.0. As a precaution, I’ve copied the website I’m upgrading to a subdomain where I can use the copy as a demo, and work out any kinks; which proved to be the right move. I’ve tried it twice now, with the same result, which is after running the installation, the site is completely inaccessible. The frontend shows «The server returned a «500 — Whoops, looks like something went wrong.»» The backend just shows «Class «JRequest» not found,» but I can’t find anything related to that with the Joomla 4 upgrade.

I ran the per-installation check. I disabled all extensions that were flagged as possible problems — I don’t know if they needed to be uninstalled completely. I’ve been checking on Joomal 4 compatibility with each of them.
The one thing in the pre-install check I couldn’t seem to address was under PHP settings, it says Display Errors is set to on, and I can’t find any option to turn it off. I got to the Server tab in Global Configuration and error reporting is set to none. I can’t find any php.ini file; and I even tried one suggestion I found of adding one with the code to set Display Errors to 0 and place it in a public_html folder in the root, but that didn’t help.
So I’m stumped if that’s the root of the issue, how to address it if it is; or what the problem might actually be.


User avatar

Per Yngve Berg

Joomla! Master
Joomla! Master
Posts: 29659
Joined: Mon Oct 27, 2008 9:27 pm
Location: Romerike, Norway

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by Per Yngve Berg » Mon Aug 08, 2022 6:14 pm

Enable Debug in configuration.php to see where the error is comming from.


stargazer1682

Joomla! Enthusiast
Joomla! Enthusiast
Posts: 177
Joined: Sat Jan 10, 2009 7:16 am

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by stargazer1682 » Mon Aug 08, 2022 6:20 pm

Per Yngve Berg wrote: ↑

Mon Aug 08, 2022 6:14 pm


Enable Debug in configuration.php to see where the error is comming from.

I can’t, that’s part of the problem. The error is showing up when I try to access the backend, but that’s all I get. It won’t let me log in or do anything.


gws

Joomla! Virtuoso
Joomla! Virtuoso
Posts: 4977
Joined: Tue Aug 23, 2005 1:56 pm
Location: South coast, UK
Contact:

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by gws » Mon Aug 08, 2022 6:58 pm

You can edit the configuration.php from your server cpanel.


User avatar

Nidzo2203

Joomla! Explorer
Joomla! Explorer
Posts: 259
Joined: Sat Nov 21, 2009 4:52 pm
Contact:

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by Nidzo2203 » Mon Aug 08, 2022 7:01 pm

Access configuration.php file with ftp client or cPanel file manager. Change permission to 644 so you can change it
In configuration.php set Debug to ‘true’ and Error reporting to ‘maximum’

Save file.


stargazer1682

Joomla! Enthusiast
Joomla! Enthusiast
Posts: 177
Joined: Sat Jan 10, 2009 7:16 am

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by stargazer1682 » Mon Aug 08, 2022 7:31 pm

Nidzo2203 wrote: ↑

Mon Aug 08, 2022 7:01 pm


Access configuration.php file with ftp client or cPanel file manager. Change permission to 644 so you can change it
In configuration.php set Debug to ‘true’ and Error reporting to ‘maximum’

Save file.

Frontend report:

Code: Select all

PrepareStatementFailureException
in .../libraries/vendor/joomla/database/src/Mysqli/MysqliStatement.php (line 141)
in .../libraries/vendor/joomla/database/src/Mysqli/MysqliDriver.php -> __construct (line 1048)
in .../libraries/vendor/joomla/database/src/DatabaseDriver.php -> prepareStatement (line 1900)
DatabaseDriver->setQuery(object(MysqliQuery))
in .../libraries/src/Menu/SiteMenu.php (line 155)
                )                ->bind(':currentDate2', $currentDate)                ->order($this->db->quoteName('m.lft'));            $items    = [];            $iterator = $this->db->setQuery($query)->getIterator();            foreach ($iterator as $item)            {                $items[$item->id] = new MenuItem((array) $item);            }
SiteMenu->JoomlaCMSMenu{closure}()
in .../libraries/src/Cache/Controller/CallbackController.php (line 52)
CallbackController->get(object(Closure), array(), 'd17e8e13b99b4d9bf23a7d0b83a466c3', false)
in .../libraries/src/Menu/SiteMenu.php (line 171)
SiteMenu->load()
in .../libraries/src/Menu/AbstractMenu.php (line 338)
AbstractMenu->getMenu()
in .../libraries/src/Menu/AbstractMenu.php (line 157)
AbstractMenu->getItem(null)
in .../libraries/src/Application/SiteApplication.php (line 429)
SiteApplication->getTemplate(true)
in .../libraries/src/Error/Renderer/HtmlRenderer.php (line 47)
HtmlRenderer->render(object(Error))
in .../libraries/src/Exception/ExceptionHandler.php (line 131)
ExceptionHandler::render(object(Error))
in .../libraries/src/Exception/ExceptionHandler.php (line 74)
ExceptionHandler::handleException(object(Error))
in .../libraries/src/Application/CMSApplication.php (line 311)
CMSApplication->execute()
in .../includes/app.php (line 63)
require_once('.../includes/app.php')
in .../index.php (line 32)

And backend

Code: Select all

#	Function	Location
1	()	JROOT/plugins/system/constantcontactapi/constantcontactapi.php:43
2	plgSystemConstantContactAPI->onAfterInitialise()	JROOT/libraries/src/Plugin/CMSPlugin.php:285
3	JoomlaCMSPluginCMSPlugin->JoomlaCMSPlugin{closure}()	JROOT/libraries/vendor/joomla/event/src/Dispatcher.php:486
4	JoomlaEventDispatcher->dispatch()	JROOT/libraries/src/Application/EventAware.php:111
5	JoomlaCMSApplicationWebApplication->triggerEvent()	JROOT/libraries/src/Application/CMSApplication.php:743
6	JoomlaCMSApplicationCMSApplication->initialiseApp()	JROOT/libraries/src/Application/AdministratorApplication.php:354
7	JoomlaCMSApplicationAdministratorApplication->initialiseApp()	JROOT/libraries/src/Application/AdministratorApplication.php:165
8	JoomlaCMSApplicationAdministratorApplication->doExecute()	JROOT/libraries/src/Application/CMSApplication.php:278
9	JoomlaCMSApplicationCMSApplication->execute()	JROOT/administrator/includes/app.php:63
10	require_once()	JROOT/administrator/index.php:32

Edited out the details of the root directory. On the backend, I see something a Constant Contact API, and I know I at least disabled that extension, if not uninstalled it before trying the upgrade. On the frontend, I honestly have no idea…


User avatar

Per Yngve Berg

Joomla! Master
Joomla! Master
Posts: 29659
Joined: Mon Oct 27, 2008 9:27 pm
Location: Romerike, Norway

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by Per Yngve Berg » Mon Aug 08, 2022 8:17 pm

Did you disable this plugin «plgSystemConstantContactAPI»?


stargazer1682

Joomla! Enthusiast
Joomla! Enthusiast
Posts: 177
Joined: Sat Jan 10, 2009 7:16 am

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by stargazer1682 » Mon Aug 08, 2022 8:25 pm

Per Yngve Berg wrote: ↑

Mon Aug 08, 2022 8:17 pm


Did you disable this plugin «plgSystemConstantContactAPI»?

I know I at least disabled it. I went through and disabled anything that was listed as a possible conflict or uncertain.


User avatar

Nidzo2203

Joomla! Explorer
Joomla! Explorer
Posts: 259
Joined: Sat Nov 21, 2009 4:52 pm
Contact:

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by Nidzo2203 » Mon Aug 08, 2022 8:52 pm

It still makes problem. Rename extension’s folder to something else.
For example constantcontactapiOLD


stargazer1682

Joomla! Enthusiast
Joomla! Enthusiast
Posts: 177
Joined: Sat Jan 10, 2009 7:16 am

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by stargazer1682 » Tue Aug 09, 2022 5:30 pm

Nidzo2203 wrote: ↑

Mon Aug 08, 2022 8:52 pm


It still makes problem. Rename extension’s folder to something else.
For example constantcontactapiOLD

That got me to where I could log into the backend, but this is all that would load:
Image

This is the same as I got immediately after each attempt to run the upgrade; and then if I’d leave and try to come back to the backend I got the previous error.

I don’t know what to do with these other errors though or to get this to where it’s working in Joomla 4…


stargazer1682

Joomla! Enthusiast
Joomla! Enthusiast
Posts: 177
Joined: Sat Jan 10, 2009 7:16 am

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by stargazer1682 » Tue Aug 09, 2022 9:14 pm

Is there a way to manually change the administrator template if you don’t have access to the backend? Digging into it more, I have reason to think that, at least the reason the backend looks like this is that the Joomla 3 isis template is not compatible with Joomla 4, in the course of the upgrade was still kept as the active template.


User avatar

sozzled

Joomla! Master
Joomla! Master
Posts: 13247
Joined: Sun Jul 05, 2009 3:30 am
Location: Canberra, Australia

Re: Change from Isis to Atum template

Post

by sozzled » Tue Aug 09, 2022 9:52 pm

Theoretically, if people use the correct method to update J! 3.10 to J! 4.x, the old J! 3.x templates should either be automatically removed or deactivated. That’s why I’m surprised that you would have the Isis template as the default for J! 4.x.

You can change the default template for J! 4.x by using phpMyAdmin and look at the table _template_styles (see the screenshot below):

changeIsis2Atum.png

Find the row relating to Isis and change the home column value from 1 to 0; find the row relating to Atum and change the home column value from 0 to 1. Once you are able to login to the backend you can then uninstall all the old J! 3.x templates used by the website.

J! 3.x templates are incompatible with J! 4.x (just like J! 2.5 templates are incompatible with J! 3.x or J!1.5 templates are incompatible with everything else).

Does that help?

You do not have the required permissions to view the files attached to this post.

“If you think I’m wrong then say, ‘I think you’re wrong.’ If you say ‘You’re wrong!’, how do you know?”
Walking the talk: https://j4xdemo.enduring.com.au
:)


stargazer1682

Joomla! Enthusiast
Joomla! Enthusiast
Posts: 177
Joined: Sat Jan 10, 2009 7:16 am

Re: Change from Isis to Atum template

Post

by stargazer1682 » Wed Aug 10, 2022 4:52 am

sozzled wrote: ↑

Tue Aug 09, 2022 9:52 pm


Theoretically, if people use the correct method to update J! 3.10 to J! 4.x, the old J! 3.x templates should either be automatically removed or deactivated. That’s why I’m surprised that you would have the Isis template as the default for J! 4.x.

You can change the default template for J! 4.x by using phpMyAdmin and look at the table _template_styles (see the screenshot below):

changeIsis2Atum.png

Find the row relating to Isis and change the home column value from 1 to 0; find the row relating to Atum and change the home column value from 0 to 1. Once you are able to login to the backend you can then uninstall all the old J! 3.x templates used by the website.

J! 3.x templates are incompatible with J! 4.x (just like J! 2.5 templates are incompatible with J! 3.x or J!1.5 templates are incompatible with everything else).

Does that help?

Okay, this is getting weird. I have two instances of attempting to get Joomla 4 work for this website; for one I used the upgrade option in the backend of the site I want to upgrade (a copy of it, anyway). The other was a fresh install of of Joomla 4 to see if it would be easier to just manually the copy the content over. The fresh install worked, but I didn’t care for the backend layout, so I tried installing the default admin template I used on Joomla 3. Probably dumb, but the upshot was, when I did that, the backend appeared the way it did after I ran the upgrade in the demo site. That’s what gave me an inkling that at least one of the problems was that the upgrade didn’t make the switch in the admin templates.
I did what you suggested and went into PHPMyAdmin. It worked in the fresh install, but for some reason it won’t show Atum in the template_styles table, even though the folder and files are in the administrator/templates folder for that instance. Something’s incomplete in the upgrade process, and I’ve already done it twice with the same result, so I don’t know what’s going on.
I’d rather not have to essentially rebuild the entire website in a fresh install, if I don’t have to. This is pretty much why I’ve been wary of switching to Joomla 4…


User avatar

sozzled

Joomla! Master
Joomla! Master
Posts: 13247
Joined: Sun Jul 05, 2009 3:30 am
Location: Canberra, Australia

Re: Change from Isis to Atum template

Post

by sozzled » Wed Aug 10, 2022 5:25 am

stargazer1682 wrote: ↑

Wed Aug 10, 2022 4:52 am

I … [had problems with one website wrecked by a badly-run update from J! 3.x to J! 4.x so I created another] fresh install of Joomla 4 to see if it would be easier to just manually the copy the content over …

I wouldn’t have recommended doing that even if there may be a dozen people who might suggest this approach.

stargazer1682 wrote: ↑

Wed Aug 10, 2022 4:52 am

The fresh install worked, but I didn’t care for the backend layout …

Well, that’s entirely a matter of personal opinion but the Atum template is what you get when you create a new website with J! 4.x. ;)

stargazer1682 wrote: ↑

Wed Aug 10, 2022 4:52 am

… so I tried installing the default admin template I used on Joomla 3.

I don’t know where you got that idea from. We’ve written dozens—if not hundreds—of times on this forum: J! 3.x templates are useless with J! 4.x. Don’t do it; don’t try to do it and, if you do it, it’s your problem. 8)

stargazer1682 wrote: ↑

Wed Aug 10, 2022 4:52 am

I did what you suggested and went into phpMyAdmin. It worked in the fresh install, but for some reason it won’t show Atum in the template_styles table, even though the folder and files are in the administrator/templates folder for that instance.

At this point in the game I’m lost. I wasn’t aware that you have (or tried) two websites and, in having two websites we’ve confused a problem in one site with a problem in another (or, confused an issue caused by doing something in one website with a non-issue in the other site). So I’m lost here and I don’t know what to advise.

Perhaps there’s someone else—more gifted than me—who can make sense of what you’re trying to describe. :pop Is it possible for you to go back to what you had before all of these problems started?

“If you think I’m wrong then say, ‘I think you’re wrong.’ If you say ‘You’re wrong!’, how do you know?”
Walking the talk: https://j4xdemo.enduring.com.au
:)


User avatar

Nidzo2203

Joomla! Explorer
Joomla! Explorer
Posts: 259
Joined: Sat Nov 21, 2009 4:52 pm
Contact:

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by Nidzo2203 » Wed Aug 10, 2022 11:54 am

Start over again. Restore J3 backup (files and database).
Post screenshot of Pre-update check here.


stargazer1682

Joomla! Enthusiast
Joomla! Enthusiast
Posts: 177
Joined: Sat Jan 10, 2009 7:16 am

Re: Change from Isis to Atum template

Post

by stargazer1682 » Wed Aug 10, 2022 1:14 pm

sozzled wrote: ↑

Wed Aug 10, 2022 5:25 am


At this point in the game I’m lost. I wasn’t aware that you have (or tried) two websites and, in having two websites we’ve confused a problem in one site with a problem in another (or, confused an issue caused by doing something in one website with a non-issue in the other site). So I’m lost here and I don’t know what to advise.

Perhaps there’s someone else—more gifted than me—who can make sense of what you’re trying to describe. :pop Is it possible for you to go back to what you had before all of these problems started?

It’s not two websites. Rather than working on the actual live site and risk it crashing and then have to screw around restoring it, I copied the files and database to a subdomain on my hosting space, where I could try the installation without any risks and work out the kinks. Then once it was actually working, I could transition the working upgraded site to being the live version. I’ve found that to be a pretty good approach, as this occasion has affirmed, because I’d probably be pretty stressed and pissed off had I crashed my client’s live site repeatedly now, with no clear reason as to why.

In this case I’ve ended up trying this two different ways. One of them being the fresh install as a subdomain.
Primarily I’ve tried the built-in upgrade from the backend — twice now, with two successive copies of the same website; both failing to upgrade. The second time I uninstalled a bunch of extensions that were flagged as possibly incompatible in the preinstall checklist. The only thing still on there that I mentioned in the OP, that hasn’t been addressed yet in this thread, is that «display errors» was set to On under php settings, and I can’t find anything about turning it off that’s actually worked.

Yet it still did the same exact thing. It doesn’t seem to actually do everything it’s supposed to do, like change the admin template, and a host of other issues I don’t even know where to start to address…


User avatar

sozzled

Joomla! Master
Joomla! Master
Posts: 13247
Joined: Sun Jul 05, 2009 3:30 am
Location: Canberra, Australia

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by sozzled » Wed Aug 10, 2022 6:38 pm

stargazer1682 wrote: ↑

Wed Aug 10, 2022 1:14 pm

Rather than working on the actual live site and risk it crashing and then have to screw around restoring it, I copied the files and database to a subdomain on my hosting space, where I could try the installation without any risks and work out the kinks.

Good strategy; that’s probably how I would go about it, too. 8)

Can we assume, therefore, that the original website still works well and that the copy of the website (before you attempted to update/migrate to J! 4.x) works just as well? ??? We need to start by identifying known points of reference.

FYI:

probability.png

which, in English, reads: «the probability of the success of migrating from J! 3.x to J! 4.x is inversely proportional to the number of J! 3.x extensions installed.» To put it another way, the chances of your success decrease the more extensions you’ve got.

You do not have the required permissions to view the files attached to this post.

“If you think I’m wrong then say, ‘I think you’re wrong.’ If you say ‘You’re wrong!’, how do you know?”
Walking the talk: https://j4xdemo.enduring.com.au
:)


stargazer1682

Joomla! Enthusiast
Joomla! Enthusiast
Posts: 177
Joined: Sat Jan 10, 2009 7:16 am

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by stargazer1682 » Fri Aug 19, 2022 12:30 am

I’m at a complete loss. I’ve tried uninstalling pretty much every extensions that comes up as either needs to be updated or unknown compatibility, same result.
I tried looking into a PHP warning in the checklist (Display error On) which didn’t pan out. In that thread I was referred to this thread: viewtopic.php?f=812&t=995776
Which linked to another thread, and I can’t tell from either of those what I’m actually supposed to be looking for.

I’ve attached screen shots of the frontend and backend after trying to upgrade. One thing that’s consistent is that it never seems to manage to install the new admin template. The folder and files are there, but it never makes it into the database.

This is the administrator/logs/joomla_update.php report:

Code: Select all

#
#<?php die('Forbidden.'); ?>
#Date: 2021-12-14 16:47:36 UTC
#Software: Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT

#Fields: datetime	priority clientip	category	message
2021-12-14T16:47:36+00:00	INFO 207.118.145.180	update	Update started by user Brian Reilly (631). Old version is 3.10.3.
2021-12-14T16:47:36+00:00	INFO 207.118.145.180	update	Downloading update file from https://downloads.joomla.org/cms/joomla3/3-10-4/Joomla_3.10.4-Stable-Update_Package.zip.
2021-12-14T16:47:38+00:00	INFO 207.118.145.180	update	File Joomla_3.10.4-Stable-Update_Package.zip downloaded.
2021-12-14T16:47:39+00:00	INFO 207.118.145.180	update	Starting installation of new version.
2021-12-14T16:47:45+00:00	INFO 207.118.145.180	update	Finalising installation.
2021-12-14T16:47:45+00:00	INFO 207.118.145.180	update	Deleting removed files and folders.
2021-12-14T16:47:45+00:00	INFO 207.118.145.180	update	Cleaning up after installation.
2021-12-14T16:47:45+00:00	INFO 207.118.145.180	update	Update to version 3.10.4 is complete.
2022-01-18T17:38:14+00:00	INFO 207.118.144.174	update	Update started by user Brian Reilly (631). Old version is 3.10.4.
2022-01-18T17:38:14+00:00	INFO 207.118.144.174	update	Downloading update file from https://downloads.joomla.org/cms/joomla3/3-10-5/Joomla_3.10.5-Stable-Update_Package.zip.
2022-01-18T17:38:20+00:00	INFO 207.118.144.174	update	File Joomla_3.10.5-Stable-Update_Package.zip downloaded.
2022-01-18T17:38:21+00:00	INFO 207.118.144.174	update	Starting installation of new version.
2022-01-18T17:38:38+00:00	INFO 207.118.144.174	update	Finalising installation.
2022-01-18T17:38:38+00:00	INFO 207.118.144.174	update	Deleting removed files and folders.
2022-01-18T17:38:39+00:00	INFO 207.118.144.174	update	Cleaning up after installation.
2022-01-18T17:38:39+00:00	INFO 207.118.144.174	update	Update to version 3.10.5 is complete.
2022-02-15T15:11:19+00:00	INFO 207.118.144.10	update	Update started by user Brian Reilly (631). Old version is 3.10.5.
2022-02-15T15:11:24+00:00	INFO 207.118.144.10	update	Downloading update file from https://downloads.joomla.org/cms/joomla3/3-10-6/Joomla_3.10.6-Stable-Update_Package.zip.
2022-02-15T15:11:30+00:00	INFO 207.118.144.10	update	File Joomla_3.10.6-Stable-Update_Package.zip downloaded.
2022-02-15T15:11:30+00:00	INFO 207.118.144.10	update	Starting installation of new version.
2022-02-15T15:11:59+00:00	INFO 207.118.144.10	update	Finalising installation.
2022-02-15T15:11:59+00:00	INFO 207.118.144.10	update	Deleting removed files and folders.
2022-02-15T15:12:00+00:00	INFO 207.118.144.10	update	Cleaning up after installation.
2022-02-15T15:12:00+00:00	INFO 207.118.144.10	update	Update to version 3.10.6 is complete.
2022-03-29T19:26:05+00:00	INFO 204.15.110.165	update	Update started by user Brian Reilly (631). Old version is 3.10.6.
2022-03-29T19:26:05+00:00	INFO 204.15.110.165	update	Downloading update file from https://s3-us-west-2.amazonaws.com/joomla-official-downloads/joomladownloads/joomla3/Joomla_3.10.7-Stable-Update_Package.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA6LXDJLNUINX2AVMH%2F20220329%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20220329T192600Z&X-Amz-Expires=60&X-Amz-SignedHeaders=host&X-Amz-Signature=f1f3dcd4682988fbdaed4a20758087a56c9378e8697152ecd1f0004945ba9b45.
2022-03-29T19:26:07+00:00	INFO 204.15.110.165	update	File Joomla_3.10.7-Stable-Update_Package.zip downloaded.
2022-03-29T19:26:07+00:00	INFO 204.15.110.165	update	Starting installation of new version.
2022-03-29T19:26:28+00:00	INFO 204.15.110.165	update	Finalising installation.
2022-03-29T19:26:28+00:00	INFO 204.15.110.165	update	Ran query from file 3.10.7-2022-02-20. Query text: DELETE FROM `#__postinstall_messages` WHERE `title_key` = 'COM_ADMIN_POSTINSTALL.
2022-03-29T19:26:28+00:00	INFO 204.15.110.165	update	Ran query from file 3.10.7-2022-03-18. Query text: ALTER TABLE `#__users` ADD COLUMN `authProvider` VARCHAR(100) NOT NULL DEFAULT '.
2022-03-29T19:26:28+00:00	INFO 204.15.110.165	update	Deleting removed files and folders.
2022-03-29T19:26:29+00:00	INFO 204.15.110.165	update	Cleaning up after installation.
2022-03-29T19:26:29+00:00	INFO 204.15.110.165	update	Update to version 3.10.7 is complete.
2022-03-30T23:55:09+00:00	INFO 207.118.145.112	update	Update started by user Brian Reilly (631). Old version is 3.10.7.
2022-03-30T23:55:10+00:00	INFO 207.118.145.112	update	Downloading update file from https://s3-us-west-2.amazonaws.com/joomla-official-downloads/joomladownloads/joomla3/Joomla_3.10.8-Stable-Update_Package.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA6LXDJLNUINX2AVMH%2F20220330%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20220330T235504Z&X-Amz-Expires=60&X-Amz-SignedHeaders=host&X-Amz-Signature=a2cfcd9c34556c3b912a32199638d0212512cc7618d3b98244f78e211ac9ab79.
2022-03-30T23:55:11+00:00	INFO 207.118.145.112	update	File Joomla_3.10.8-Stable-Update_Package.zip downloaded.
2022-03-30T23:55:11+00:00	INFO 207.118.145.112	update	Starting installation of new version.
2022-03-30T23:55:25+00:00	INFO 207.118.145.112	update	Finalising installation.
2022-03-30T23:55:25+00:00	INFO 207.118.145.112	update	Deleting removed files and folders.
2022-03-30T23:55:26+00:00	INFO 207.118.145.112	update	Cleaning up after installation.
2022-03-30T23:55:26+00:00	INFO 207.118.145.112	update	Update to version 3.10.8 is complete.
2022-05-10T20:10:03+00:00	INFO 24.177.149.113	update	Update started by user Brian Reilly (631). Old version is 3.10.8.
2022-05-10T20:10:04+00:00	INFO 24.177.149.113	update	Downloading update file from https://s3-us-west-2.amazonaws.com/joomla-official-downloads/joomladownloads/joomla3/Joomla_3.10.9-Stable-Update_Package.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA6LXDJLNUINX2AVMH%2F20220510%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20220510T201004Z&X-Amz-Expires=60&X-Amz-SignedHeaders=host&X-Amz-Signature=da4dc57b89a2b88d877558115cc7b2fc6bd2b4d642d2a4165a160611c0cf081f.
2022-05-10T20:10:06+00:00	INFO 24.177.149.113	update	File Joomla_3.10.9-Stable-Update_Package.zip downloaded.
2022-05-10T20:10:07+00:00	INFO 24.177.149.113	update	Starting installation of new version.
2022-05-10T20:12:25+00:00	INFO 24.177.149.113	update	Finalising installation.
2022-05-10T20:12:25+00:00	INFO 24.177.149.113	update	Deleting removed files and folders.
2022-05-10T20:12:26+00:00	INFO 24.177.149.113	update	Cleaning up after installation.
2022-05-10T20:12:26+00:00	INFO 24.177.149.113	update	Update to version 3.10.9 is complete.
2022-06-21T20:22:49+00:00	INFO 207.118.145.58	update	Update started by user Brian Reilly (631). Old version is 3.10.9.
2022-06-21T20:22:50+00:00	INFO 207.118.145.58	update	Downloading update file from https://s3-us-west-2.amazonaws.com/joomla-official-downloads/joomladownloads/joomla3/Joomla_3.10.10-Stable-Update_Package.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA6LXDJLNUINX2AVMH%2F20220621%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20220621T202249Z&X-Amz-Expires=60&X-Amz-SignedHeaders=host&X-Amz-Signature=6f9db82236db5bc4248a7f9664a76ccc46efb9c10db89d9d03930758bfaf1ee7.
2022-06-21T20:22:52+00:00	INFO 207.118.145.58	update	File Joomla_3.10.10-Stable-Update_Package.zip downloaded.
2022-06-21T20:22:52+00:00	INFO 207.118.145.58	update	Starting installation of new version.
2022-06-21T20:23:20+00:00	INFO 207.118.145.58	update	Finalising installation.
2022-06-21T20:23:20+00:00	INFO 207.118.145.58	update	Deleting removed files and folders.
2022-06-21T20:23:21+00:00	INFO 207.118.145.58	update	Cleaning up after installation.
2022-06-21T20:23:21+00:00	INFO 207.118.145.58	update	Update to version 3.10.10 is complete.
2022-08-16T22:37:58+00:00	INFO 207.118.145.27	update	Update started by user Brian Reilly (631). Old version is 3.10.10.
2022-08-16T22:37:59+00:00	INFO 207.118.145.27	update	Downloading update file from https://s3-us-west-2.amazonaws.com/joomla-official-downloads/joomladownloads/joomla3/Joomla_3.10.11-Stable-Update_Package.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA6LXDJLNUINX2AVMH%2F20220816%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20220816T223825Z&X-Amz-Expires=60&X-Amz-SignedHeaders=host&X-Amz-Signature=cc34a5634368f3f266fdb56c7d1248d92295c2e6d653b5b4e20a86ac79d8660d.
2022-08-16T22:38:00+00:00	INFO 207.118.145.27	update	File Joomla_3.10.11-Stable-Update_Package.zip downloaded.
2022-08-16T22:38:01+00:00	INFO 207.118.145.27	update	Starting installation of new version.
2022-08-16T22:38:18+00:00	INFO 207.118.145.27	update	Update started by user Brian Reilly (631). Old version is 3.10.10.
2022-08-16T22:38:19+00:00	INFO 207.118.145.27	update	File Joomla_3.10.11-Stable-Update_Package.zip downloaded.
2022-08-16T22:38:19+00:00	INFO 207.118.145.27	update	Starting installation of new version.
2022-08-16T22:38:55+00:00	INFO 207.118.145.27	update	Finalising installation.
2022-08-16T22:38:55+00:00	INFO 207.118.145.27	update	Deleting removed files and folders.
2022-08-16T22:38:56+00:00	INFO 207.118.145.27	update	Cleaning up after installation.
2022-08-16T22:38:56+00:00	INFO 207.118.145.27	update	Update to version 3.10.11 is complete.
2022-08-18T21:00:44+00:00	INFO 207.118.145.27	update	Update started by user Brian Reilly (631). Old version is 3.10.11.
2022-08-18T21:00:44+00:00	INFO 207.118.145.27	update	Downloading update file from https://s3-us-west-2.amazonaws.com/joomla-official-downloads/joomladownloads/joomla4/Joomla_4.1.5-Stable-Update_Package.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA6LXDJLNUINX2AVMH%2F20220818%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20220818T210109Z&X-Amz-Expires=60&X-Amz-SignedHeaders=host&X-Amz-Signature=4895319ed95e3e4e6d1503c9f4106d5a1859f0eb7b9f5e5090e9de32e86fdece.
2022-08-18T21:00:46+00:00	INFO 207.118.145.27	update	File Joomla_4.1.5-Stable-Update_Package.zip downloaded.
2022-08-18T21:00:46+00:00	INFO 207.118.145.27	update	Starting installation of new version.

I’ve lost track of the number of times I’ve tried running the installation at this point.
One thing that I don’t know if it’s unrelated or possibly the issue — before upgrading, in Extensions Manager, there’s a single instance of a for the admin component of EasyBlog. I can’t get rid of it. The component should have been uninstalled ages ago. I can’t even find the installer (at least not one compatible with Joomla 3). There no files related to this in any directory I look in, and it doesn’t come up in the database; so I have no idea how to remove it manually, and the automatic uninstall won’t work… It might be completely unrelated the Joomla 4 upgrade; I’m just grasping at straws…

You do not have the required permissions to view the files attached to this post.


User avatar

Nidzo2203

Joomla! Explorer
Joomla! Explorer
Posts: 259
Joined: Sat Nov 21, 2009 4:52 pm
Contact:

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by Nidzo2203 » Fri Aug 19, 2022 4:23 am

Why don’t you try upgrading on your PC/Laptop?
Install WAMP server on your computer, download copy of your J3 site and database and try to upgrade.



stargazer1682

Joomla! Enthusiast
Joomla! Enthusiast
Posts: 177
Joined: Sat Jan 10, 2009 7:16 am

Re: JoomlaDatabaseExceptionPrepareStatementFailureException: Unknown column ‘m.publish_up’ in ‘where clause’

Post

by stargazer1682 » Fri Aug 19, 2022 8:02 pm

sozzled wrote: ↑

Fri Aug 19, 2022 5:46 am

JoomlaDatabaseExceptionPrepareStatementFailureException:
Unknown column ‘m.publish_up’ in ‘where clause’

… see viewtopic.php?f=812&t=995776

Yes, that’s literally the link I posted in my last comment, that I’ve already looked at. As far as I can tell, that thread reaches no actual solution; and passes them on to yet another thread, that also doesn’t appear to be helpful. Both have a lot of code, but the closest thing I can find in the second thread is that they tried uninstalling one or all but one of their templates, which I just tried and still no luck. This is actually becoming very frustrating, because all of the resources keep saying that this should be incredibly easy, and it’s anything but — which is also why I’ve been reluctant to even try, because I saw this coming a mile away.
The installation doesn’t even seem to be starting. It doesn’t install Atum, there’s not even any changes being made to the database, because at this point all I’ve had to do to restore the clone/demo version of the site is replace the files with copies of the original and it’s back to J3 in a snap.
I’ve tried uninstalling every extension — which I shouldn’t even have to try, otherwise I might as well just start with a fresh install — but even then it still isn’t working. It’s not even creating a joomla_update.php log most of the time.
I even tried doing an upload and install, first with the latest stable version of J4, then going back and trying Joomla 4.0. 4.0 got me closer to actually being able to do anything in the backend, but it’s still completely broken.


User avatar

Per Yngve Berg

Joomla! Master
Joomla! Master
Posts: 29659
Joined: Mon Oct 27, 2008 9:27 pm
Location: Romerike, Norway

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by Per Yngve Berg » Sat Aug 20, 2022 12:49 pm

This site appears to have multiple issues.
I suggest you use the Forum Post Assistant so we can review your server config and extensions installed. See red frame above.


stargazer1682

Joomla! Enthusiast
Joomla! Enthusiast
Posts: 177
Joined: Sat Jan 10, 2009 7:16 am

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by stargazer1682 » Sat Aug 20, 2022 3:46 pm

Per Yngve Berg wrote: ↑

Sat Aug 20, 2022 12:49 pm


This site appears to have multiple issues.
I suggest you use the Forum Post Assistant so we can review your server config and extensions installed. See red frame above.

Looks like the script is working. Hopefully I put it in the right place and isn’t too compromising. This is the cloned site that had a failed upgrade attempt.
https://joom42.ourbetterangels.org/Foru … fpa-en.php


stargazer1682

Joomla! Enthusiast
Joomla! Enthusiast
Posts: 177
Joined: Sat Jan 10, 2009 7:16 am

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by stargazer1682 » Sun Aug 21, 2022 7:03 pm

Does the Forum Post Assistant show any insightful information? I can’t make heads or tails of it.


User avatar

Per Yngve Berg

Joomla! Master
Joomla! Master
Posts: 29659
Joined: Mon Oct 27, 2008 9:27 pm
Location: Romerike, Norway

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by Per Yngve Berg » Sun Aug 21, 2022 7:27 pm

Here we go:

Forum Post Assistant (v1.6.5) : 21-Aug-2022 wrote:

Basic Environment :: wrote:Joomla! Instance :: Not Found
Joomla! Configured :: Not Found

Host Configuration :: OS: Linux | OS Version: 4.4.302-icpu-083 | Technology: x86_64 | Web Server: Apache | Encoding: gzip, deflate, br | System TMP Writable: Yes | Free Disk Space : 975.80 GiB |

PHP Configuration :: Version: 8.0.22 | PHP API: cgi-fcgi | Session Path Writable: Yes | Display Errors: 0 | Error Reporting: 22517 | Log Errors To: | Last Known Error: | Register Globals: | Magic Quotes: | Safe Mode: | Allow url fopen: 1 | Open Base: | Uploads: 1 | Max. Upload Size: 64M | Max. POST Size: 64M | Max. Input Time: -1 | Max. Execution Time: 50000 | Memory Limit: -1

Database Configuration :: Database Credentials incomplete or not available Nothing to display.
User Privileges : Unknown

Detailed Environment :: wrote:PHP Extensions :: Core (8.0.22) | date (8.0.22) | libxml (8.0.22) | openssl (8.0.22) | pcre (8.0.22) | sqlite3 (8.0.22) | zlib (8.0.22) | bcmath (8.0.22) | bz2 (8.0.22) | calendar (8.0.22) | ctype (8.0.22) | curl (8.0.22) | dba (8.0.22) | dom (20031129) | hash (8.0.22) | fileinfo (8.0.22) | filter (8.0.22) | ftp (8.0.22) | gd (8.0.22) | gettext (8.0.22) | gmp (8.0.22) | SPL (8.0.22) | iconv (8.0.22) | session (8.0.22) | intl (8.0.22) | json (8.0.22) | mbstring (8.0.22) | standard (8.0.22) | PDO (8.0.22) | mysqlnd (mysqlnd 8.0.22) | pdo_sqlite (8.0.22) | Phar (8.0.22) | posix (8.0.22) | Reflection (8.0.22) | imap (8.0.22) | shmop (8.0.22) | SimpleXML (8.0.22) | soap (8.0.22) | sodium (8.0.22) | pdo_mysql (8.0.22) | exif (8.0.22) | tidy (8.0.22) | tokenizer (8.0.22) | xml (8.0.22) | xmlreader (8.0.22) | xmlwriter (8.0.22) | xsl (8.0.22) | zip (1.19.5) | mysqli (8.0.22) | cgi-fcgi (8.0.22) | Zend Engine (4.0.22) |
Potential Missing Extensions :: mysql | mcrypt |

Switch User Environment :: PHP CGI: Yes | Server SU: Yes | PHP SU: Yes | Potential Ownership Issues: Unknown


User avatar

Per Yngve Berg

Joomla! Master
Joomla! Master
Posts: 29659
Joined: Mon Oct 27, 2008 9:27 pm
Location: Romerike, Norway

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by Per Yngve Berg » Sun Aug 21, 2022 7:38 pm

The server looks OK, except that there is no Joomla.


stargazer1682

Joomla! Enthusiast
Joomla! Enthusiast
Posts: 177
Joined: Sat Jan 10, 2009 7:16 am

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by stargazer1682 » Sun Aug 21, 2022 7:56 pm

Per Yngve Berg wrote: ↑

Sun Aug 21, 2022 7:38 pm


The server looks OK, except that there is no Joomla.

I honestly don’t know what to make of that. This the assistant was added to an instance of the site after (an attempted) install of Joomla 4. All of the files are there, it just completely breaks down.


User avatar

Per Yngve Berg

Joomla! Master
Joomla! Master
Posts: 29659
Joined: Mon Oct 27, 2008 9:27 pm
Location: Romerike, Norway

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by Per Yngve Berg » Sun Aug 21, 2022 8:04 pm

The FPA didn»t find a configuration.php file in the folder where it’s located.


stargazer1682

Joomla! Enthusiast
Joomla! Enthusiast
Posts: 177
Joined: Sat Jan 10, 2009 7:16 am

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by stargazer1682 » Sun Aug 21, 2022 8:26 pm

Per Yngve Berg wrote: ↑

Sun Aug 21, 2022 8:04 pm


The FPA didn»t find a configuration.php file in the folder where it’s located.

It’s definitely there (see attached screenshot).

You do not have the required permissions to view the files attached to this post.


User avatar

Per Yngve Berg

Joomla! Master
Joomla! Master
Posts: 29659
Joined: Mon Oct 27, 2008 9:27 pm
Location: Romerike, Norway

Re: Migration to Joomla 4 Failed — Class «JRequest» not found

Post

by Per Yngve Berg » Sun Aug 21, 2022 8:33 pm

Yes, but the FPA is not in the same folder.



Return to “Migrating and Upgrading to Joomla! 4.x”


Jump to

  • Joomla! Announcements
  • ↳   Announcements
  • ↳   Announcements Discussions
  • Joomla! 4.x — Ask Support Questions Here
  • ↳   General Questions/New to Joomla! 4.x
  • ↳   Installation Joomla! 4.x
  • ↳   Administration Joomla! 4.x
  • ↳   Migrating and Upgrading to Joomla! 4.x
  • ↳   Extensions for Joomla! 4.x
  • ↳   Security in Joomla! 4.x
  • ↳   Templates for Joomla! 4.x
  • ↳   Search Engine Optimization (Joomla! SEO) in Joomla! 4.x
  • ↳   Language — Joomla! 4.x
  • ↳   Performance — Joomla! 4.x
  • ↳   Joomla! 4.x Coding
  • Joomla! 3.x — Ask Support Questions Here
  • ↳   General Questions/New to Joomla! 3.x
  • ↳   Installation Joomla! 3.x
  • ↳   Joomla! 3.x on IIS webserver
  • ↳   Administration Joomla! 3.x
  • ↳   Access Control List (ACL) in Joomla! 3.x
  • ↳   Migrating and Upgrading to Joomla! 3.x
  • ↳   Security in Joomla! 3.x
  • ↳   Extensions for Joomla! 3.x
  • ↳   Templates for Joomla! 3.x
  • ↳   Search Engine Optimization (Joomla! SEO) in Joomla! 3.x
  • ↳   Language — Joomla! 3.x
  • ↳   Performance — Joomla! 3.x
  • ↳   Joomla! 3.x Coding
  • Joomla! Versions which are End of Life
  • ↳   Joomla! 2.5 — End of Life 31 Dec 2014
  • ↳   General Questions/New to Joomla! 2.5
  • ↳   Installation Joomla! 2.5
  • ↳   Joomla! 2.5 on IIS webserver
  • ↳   Administration Joomla! 2.5
  • ↳   Access Control List (ACL) in Joomla! 2.5
  • ↳   Migrating and Upgrading to Joomla! 2.5
  • ↳   Security in Joomla! 2.5
  • ↳   Extensions for Joomla! 2.5
  • ↳   Templates for Joomla! 2.5
  • ↳   Search Engine Optimization (Joomla! SEO) in Joomla! 2.5
  • ↳   Language — Joomla! 2.5
  • ↳   Performance — Joomla! 2.5
  • ↳   Joomla! 1.5 — End of Life Sep 2012
  • ↳   General Questions/New to Joomla! 1.5
  • ↳   Installation 1.5
  • ↳   Joomla! 1.5 on IIS webserver
  • ↳   Administration 1.5
  • ↳   Migrating and Upgrading to Joomla! 1.5
  • ↳   Security in Joomla! 1.5
  • ↳   Extensions for Joomla! 1.5
  • ↳   Templates for Joomla! 1.5
  • ↳   Search Engine Optimization (Joomla! SEO) in Joomla! 1.5
  • ↳   Language — Joomla! 1.5
  • ↳   Performance — Joomla! 1.5
  • ↳   Joomla! 1.0 — End of Life 22 July 2009
  • ↳   Installation — 1.0.x
  • ↳   Upgrading — 1.0.x
  • ↳   Security — 1.0.x
  • ↳   3rd Party/Non Joomla! Security Issues
  • ↳   Administration — 1.0.x
  • ↳   Extensions — 1.0.x
  • ↳   Components
  • ↳   Modules
  • ↳   Plugins/Mambots
  • ↳   WYSIWYG Editors — 1.0.x
  • ↳   Integration & Bridges — 1.0.x
  • ↳   phpbb — Joomla! Integration
  • ↳   Templates & CSS — 1.0.x
  • ↳   Language — 1.0.x
  • ↳   Joom!Fish and Multilingual Sites
  • ↳   Performance — 1.0.x
  • ↳   General Questions — 1.0.x
  • Joomla! International Language Support
  • ↳   International Zone
  • ↳   Arabic Forum
  • ↳   تنبيهات هامة
  • ↳   الدروس
  • ↳   4.x جوملا!
  • ↳   جوملا! 1.6/1.7
  • ↳   الأسئلة الشائعة
  • ↳   التثبيت و الترقية
  • ↳   الحماية — و تحسين السرعة والأداء
  • ↳   لوحة التحكم
  • ↳   الإضافات البرمجية
  • ↳   تعريب جوملا! و الإضافات البرمجية
  • ↳   القوالب و التصميم
  • ↳   صداقة محركات البحث
  • ↳   القسم العام
  • ↳   1.5 !جوملا
  • ↳   الأسئلة الشائعة
  • ↳   التثبيت و الترقية
  • ↳   الحماية — و تحسين السرعة والأداء
  • ↳   لوحة التحكم
  • ↳   الإضافات البرمجية
  • ↳   تعريب جوملا! و الإضافات البرمجية
  • ↳   القوالب و التصميم
  • ↳   صداقة محركات البحث
  • ↳   القسم العام
  • ↳   جوملا! 1.0
  • ↳   الأسئلة الشائـعة
  • ↳   التثبيت
  • ↳   لوحة التحكم
  • ↳   الإضافات البرمجية
  • ↳   الإضافات المعرّبة
  • ↳   القوالب و التصميم
  • ↳   الحماية — تحسين السرعة والأداء — صداقة محركات البحث
  • ↳   القسم العام
  • ↳   القسم العام
  • ↳   !عرض موقعك بجوملا
  • ↳   الأرشيف
  • ↳   Bengali Forum
  • ↳   Bosnian Forum
  • ↳   Joomla! 1.5
  • ↳   Instalacija i prvi koraci
  • ↳   Ekstenzije
  • ↳   Templejti
  • ↳   Moduli
  • ↳   Prevodi i dokumentacija
  • ↳   Joomla! 1.7 / Joomla! 1.6
  • ↳   Catalan Forum
  • ↳   Notícies
  • ↳   Temes sobre l’administració
  • ↳   Temes sobre la traducció
  • ↳   Components, mòduls i joombots
  • ↳   Temes de disseny
  • ↳   Webs realitzades amb Joomla!
  • ↳   Offtopics
  • ↳   Chinese Forum
  • ↳   Croatian Forum
  • ↳   Danish Forum
  • ↳   Meddelelser
  • ↳   Joomla! 4.x
  • ↳   Joomla! 3.x (Anbefalet til nye installationer. Nyeste funktionalitet)
  • ↳   Installation, backup, opdatering og flytning — Godt igang
  • ↳   Administration — Generel brug
  • ↳   Komponenter, Moduler og Plugins
  • ↳   Template, CSS og Design
  • ↳   Nethandel, betaling m.m.
  • ↳   Ældre versioner (disse vedligeholdes ikke længere fra officiel side)
  • ↳   Joomla! 2.5 (Supporteres indtil 31. dec. 2014)
  • ↳   Installation, backup, opdatering og flytning — Godt igang
  • ↳   Administration — Generel brug
  • ↳   Komponenter, Moduler og Plugins
  • ↳   Template, CSS og Design
  • ↳   Nethandel, betaling m.m.
  • ↳   Joomla 1.5 (Tidligere langtidssupporteret version indtil sep. 2012)
  • ↳   Installation, backup, opdatering og flytning — Godt igang
  • ↳   Administration — Generel brug
  • ↳   Komponenter, Moduler og Plugins
  • ↳   Template, CSS og Design
  • ↳   Nethandel, betaling m.m.
  • ↳   Joomla 1.0 (Udgået version, der blev afløst af 1.5 i 2008)
  • ↳   Installation, backup, opdatering og flytning — Godt igang
  • ↳   Administration — Generel brug
  • ↳   Komponenter, Moduler og Mambots
  • ↳   Template, CSS og Design
  • ↳   Nethandel, betaling m.m.
  • ↳   Oversættelser (lokalisering)
  • ↳   Joomla brugergrupper i Danmark
  • ↳   JUG Kolding
  • ↳   JUG København
  • ↳   JUG Odense
  • ↳   JUG Århus
  • ↳   JUG Sorø
  • ↳   Kommerciel (betalt) hjælp ønskes
  • ↳   SEO
  • ↳   FAQ — Dokumentation og vejledninger
  • ↳   Vis dit websted
  • ↳   Afviste ‘Vis dit websted’ indlæg
  • ↳   Diverse (Off topic)
  • ↳   Dutch Forum
  • ↳   Aankondigingen
  • ↳   Algemene vragen
  • ↳   Joomla! 4.x
  • ↳   Joomla! 3.x
  • ↳   Installatie 3.x
  • ↳   Extensies 3.x
  • ↳   Templates 3.x
  • ↳   Joomla! 2.5
  • ↳   Installatie 2.5
  • ↳   Componenten 2.5
  • ↳   Modules 2.5
  • ↳   Plugins 2.5
  • ↳   Templates 2.5
  • ↳   Joomla! 1.5
  • ↳   Installatie
  • ↳   Componenten
  • ↳   Modules
  • ↳   Plugins
  • ↳   Templates
  • ↳   Joomla! 1.0
  • ↳   Installatie 1.0.x
  • ↳   Componenten 1.0.x
  • ↳   Modules 1.0.x
  • ↳   Mambots 1.0.x
  • ↳   Templates 1.0.x
  • ↳   Vertalingen
  • ↳   Offtopic
  • ↳   Show jouw website
  • ↳   Filipino Forum
  • ↳   International Support Center
  • ↳   Pinoy General Discussion & Archives
  • ↳   Site Showcase
  • ↳   Events
  • ↳   Design Tips and Tricks
  • ↳   Tsismis Zone
  • ↳   Pinoy Translation Zone
  • ↳   Pinoy Forum Archives
  • ↳   Joomla! Philippines Local Forum www.joomla.org.ph
  • ↳   Finnish Forum
  • ↳   French Forum
  • ↳   Les annonces!
  • ↳   Le bistrot!
  • ↳   L’expo!
  • ↳   J! 4.x — L’atelier!
  • ↳   J! 3.x — L’atelier!
  • ↳   3.x — Questions générales, nouvel utilisateur
  • ↳   3.x — Installation, migration et mise à jour
  • ↳   3.x — Sécurité et performances
  • ↳   3.x — Extensions tierce partie
  • ↳   3.x — Templates et design
  • ↳   3.x — Développement
  • ↳   3.x — Ressources
  • ↳   J! 2.5.x — L’atelier!
  • ↳   2.5 — Questions générales
  • ↳   2.5 — Installation, migration et mise à jour
  • ↳   2.5 — Sécurité et performances
  • ↳   2.5 — Extensions tierce partie
  • ↳   2.5 — Templates et design
  • ↳   2.5 — Développement
  • ↳   2.5 — Ressources
  • ↳   J! 1.5.x — L’atelier!
  • ↳   1.5 — Questions générales
  • ↳   1.5 — Installation, migration et mise à jour
  • ↳   1.5 — Sécurité et performances
  • ↳   1.5 — Extensions tierce partie
  • ↳   1.5 — Templates et design
  • ↳   1.5 — Développement
  • ↳   1.5 — Ressources
  • ↳   J! 1.0.x — L’atelier!
  • ↳   1.0 — Questions générales
  • ↳   1.0 — Installation et mise à jour
  • ↳   1.0 — Sécurité
  • ↳   1.0 — Extensions tierce partie
  • ↳   1.0 — Templates et design
  • ↳   1.0 — Développement
  • ↳   1.0 — Ressources
  • ↳   Besoin d’un professionel ?
  • ↳   Extensions Open Source pour Joomla!
  • ↳   German Forum
  • ↳   Ankündigungen
  • ↳   Joomla! 4.x
  • ↳   Joomla! 3.x
  • ↳   Allgemeine Fragen
  • ↳   Installation und erste Schritte
  • ↳   Komponenten, Module, Plugins
  • ↳   Template, CSS und Designfragen
  • ↳   Entwicklerforum
  • ↳   Zeige Deine Webseite
  • ↳   Joomla! 2.5
  • ↳   Allgemeine Fragen
  • ↳   Installation und erste Schritte
  • ↳   Komponenten, Module, Plugins
  • ↳   Template, CSS und Designfragen
  • ↳   Entwicklerforum
  • ↳   Zeige Deine Webseite
  • ↳   Joomla! 1.5
  • ↳   Allgemeine Fragen
  • ↳   Installation und erste Schritte
  • ↳   Komponenten, Module, Plugins
  • ↳   Template, CSS und Designfragen
  • ↳   Entwicklerforum
  • ↳   Zeige Deine Webseite
  • ↳   Professioneller Service
  • ↳   Sonstiges (Offtopic)
  • ↳   Archiv
  • ↳   Joomla! 1.0
  • ↳   Allgemeine Fragen 1.0.x
  • ↳   Installation und erste Schritte 1.0.x
  • ↳   Komponenten, Module, Mambots 1.0.x
  • ↳   Template, CSS und Designfragen 1.0.x
  • ↳   Entwicklerforum 1.0.x
  • ↳   Zeige Deine Webseite 1.0.x
  • ↳   Greek Forum
  • ↳   Joomla! 4.x
  • ↳   Joomla! 3.x
  • ↳   Joomla! 2.5.x
  • ↳   Joomla! 1.5.x
  • ↳   Joomla! 1.0.x
  • ↳   Hebrew Forum
  • ↳   Indic Languages Forum
  • ↳   Indonesian Forum
  • ↳   FAQ
  • ↳   Bantuan
  • ↳   Komponen
  • ↳   Modul
  • ↳   Template
  • ↳   Diskusi
  • ↳   Italian Forum
  • ↳   Guide
  • ↳   Traduzioni
  • ↳   Componenti — Moduli — Plugins
  • ↳   Template — Grafica
  • ↳   Notizie
  • ↳   Prodotti Open Source per Joomla!
  • ↳   Richieste professionali
  • ↳   Joomla! 4.x
  • ↳   Joomla! 3.x
  • ↳   Joomla! 2.5.x
  • ↳   Joomla! 1.x
  • ↳   Latvian Forum
  • ↳   Lithuanian Forum
  • ↳   Joomla! 4.x
  • ↳   Joomla! 1.5
  • ↳   Joomla! 1.7 / Joomla! 1.6
  • ↳   Joomla! 1.0
  • ↳   Vertimai ir Kalba
  • ↳   Malaysian Forum
  • ↳   Solved
  • ↳   Norwegian Forum
  • ↳   Informasjon
  • ↳   Arkiverte annonseringer
  • ↳   FAQ — Ofte spurte spørsmål
  • ↳   Arkiv
  • ↳   Joomla! 4.x
  • ↳   Joomla! 3.x
  • ↳   Administrasjon/installasjon
  • ↳   Migrering/Oppdatering
  • ↳   Template, CSS og design
  • ↳   Komponenter/moduler/programutvidelser
  • ↳   Sikkerhet
  • ↳   Generelt
  • ↳   Netthandel, betaling m.m.
  • ↳   VirtueMart
  • ↳   Andre nettbutikkløsninger
  • ↳   Generelt
  • ↳   Oversettelser
  • ↳   Fremvisning av sider (Show off)
  • ↳   Avviste fremvisninger
  • ↳   Diverse (off topic)
  • ↳   Kommersiell hjelp ønskes
  • ↳   Eldre versjoner av Joomla!
  • ↳   Joomla! 1.0
  • ↳   Administrasjon/installasjon
  • ↳   Template, CSS og design
  • ↳   Komponenter/moduler/mambots
  • ↳   Sikkerhet
  • ↳   Generelt
  • ↳   Joomla! 1.5
  • ↳   Administrasjon/installasjon
  • ↳   Migrering/Oppdatering
  • ↳   Template, CSS og design
  • ↳   Komponenter/moduler/programutvidelser
  • ↳   Sikkerhet
  • ↳   Generelt
  • ↳   Joomla! 2.5
  • ↳   Administrasjon/installasjon
  • ↳   Migrering/Oppdatering
  • ↳   Template, CSS og design
  • ↳   Komponenter/moduler/programutvidelser
  • ↳   Sikkerhet
  • ↳   Generelt
  • ↳   Persian Forum
  • ↳   قالب ها
  • ↳   مدیریت
  • ↳   سوالهای عمومی
  • ↳   نصب
  • ↳   مامبوت ها
  • ↳   ماژولها
  • ↳   کامپوننت ها
  • ↳   Polish Forum
  • ↳   Instalacja i aktualizacja
  • ↳   Administracja
  • ↳   Komponenty, moduły, wtyczki
  • ↳   Szablony
  • ↳   Paczta i Podziwiajta
  • ↳   Modyfikacje i własne rozwiązania
  • ↳   Tłumaczenia
  • ↳   FAQ
  • ↳   Tips&Tricks
  • ↳   Dokumentacja
  • ↳   Profesjonalne usługi
  • ↳   Portuguese Forum
  • ↳   Componentes, módulos e mambots
  • ↳   Programação e desenvolvimento
  • ↳   Segurança
  • ↳   Sites dos usuários
  • ↳   Off-topic
  • ↳   Tradução
  • ↳   Templates
  • ↳   Romanian Forum
  • ↳   Traduceri
  • ↳   Russian Forum
  • ↳   Объявления по Joomla!
  • ↳   Безопасность Joomla!
  • ↳   Joomla 4.x — Задайте здесь свой вопрос по поддержке
  • ↳   Joomla 3.x — Задайте здесь свой вопрос по поддержке
  • ↳   Общие вопросы/Новичок в Joomla! 3.x
  • ↳   Установка Joomla! 3.x
  • ↳   Миграция и переход на Joomla! 3.x
  • ↳   Расширения для Joomla! 3.x
  • ↳   Многоязычные веб-сайты на Joomla 3.x
  • ↳   Joomla 2.5 — Задайте здесь свой вопрос по поддержке
  • ↳   Общие вопросы/Новичок в Joomla! 2.5
  • ↳   Установка Joomla! 2.5
  • ↳   Расширения для Joomla! 2.5
  • ↳   Русский язык Joomla! 2.5
  • ↳   Serbian/Montenegrin Forum
  • ↳   Tehnička pitanja
  • ↳   Instalacija i početnička pitanja
  • ↳   Šabloni
  • ↳   Prevod i dokumentacija
  • ↳   Ćaskanje
  • ↳   Bezbednost
  • ↳   Joomla! dodaci
  • ↳   Pravna pitanja
  • ↳   Arhiva
  • ↳   Joomla! Događaji i Zajednica
  • ↳   Izlog (spisak) sajtova radjenih u Joomla! CMS-u
  • ↳   Profesionalne usluge
  • ↳   Slovak Forum
  • ↳   Spanish Forum
  • ↳   Joomla! 4.x
  • ↳   Joomla! 3.x
  • ↳   Migración y actualización a Joomla 3.x
  • ↳   Versiones de Joomla! obsoletas
  • ↳   Joomla! 2.5
  • ↳   Joomla! 1.5
  • ↳   Extensiones
  • ↳   Plantillas (templates) y diseño
  • ↳   Idioma y traducciones
  • ↳   SEO para Joomla!
  • ↳   Seguridad y rendimiento
  • ↳   Productos de Código Abierto para Joomla!
  • ↳   Servicios profesionales
  • ↳   Salón de la comunidad Ñ
  • ↳   Swedish Forum
  • ↳   Meddelanden
  • ↳   Forum Joomla! 4.x
  • ↳   Forum Joomla! 3.x
  • ↳   Allmänna frågor
  • ↳   Användning och administration
  • ↳   Installation, backup och säkerhet
  • ↳   Komponenter, moduler och plugin
  • ↳   Mallar (templates) och design
  • ↳   Äldre versioner
  • ↳   Forum Joomla! 1.0
  • ↳   Allmänna frågor
  • ↳   Användning och administration
  • ↳   Installation, backup och säkerhet
  • ↳   Komponenter, moduler och Mambots
  • ↳   Mallar (templates) och design
  • ↳   Forum Joomla! 1.7 / Joomla! 1.6
  • ↳   Allmänna frågor
  • ↳   Användning och administration
  • ↳   Installation, backup och säkerhet
  • ↳   Komponenter, moduler och plugin
  • ↳   Mallar (templates) och design
  • ↳   Forum Joomla! 1.5
  • ↳   Allmänna frågor
  • ↳   Användning och administration
  • ↳   Installation, backup och säkerhet
  • ↳   Komponenter, moduler och plugin
  • ↳   Mallar (templates) och design
  • ↳   Forum Joomla! 2.5
  • ↳   Allmänna frågor
  • ↳   Användning och administration
  • ↳   Installation, backup och säkerhet
  • ↳   Komponenter, moduler och plugin
  • ↳   Mallar (templates) och design
  • ↳   Översättning
  • ↳   Webbplatser gjorda i Joomla
  • ↳   Webbplatser J! 3.x
  • ↳   Webbplatser J! 2.5
  • ↳   Webbplatser Joomla! 1.7 / Joomla! 1.6
  • ↳   Webbplatser J! 1.5
  • ↳   Webbplatser J! 1.0
  • ↳   Kommersiell hjälp önskas
  • ↳   Diverse (off topic)
  • ↳   Tamil Forum
  • ↳   Thai Forum
  • ↳   โชว์เว็บไซต์ของคุณที่สร้างด้วยจูมล่า
  • ↳   เคล็ดลับการใช้งานส่วนต่างๆ เกี่ยวกับจ&#
  • ↳   คอมโพเน้นท์ โมดูล ปลักอิน ต่างๆ ที่ติดตั
  • ↳   อับเดดข่าวสารเกี่ยวกับจูมล่าลายไทย
  • ↳   Turkish Forum
  • ↳   Duyurular
  • ↳   Dersler
  • ↳   Genel Sorular
  • ↳   Bileşen, Modül, Bot
  • ↳   Eklenti Haberleri
  • ↳   Temalar
  • ↳   Vietnamese Forum
  • ↳   Gặp gỡ và giao lưu
  • ↳   Joomla Tiếng Việt
  • ↳   Cài đặt — Cấu hình
  • ↳   Thành phần mở rộng cho Joomla!
  • ↳   Hỏi đáp Joomla! 3.x
  • ↳   Hỏi đáp Joomla! 2.5
  • ↳   Hỗ trợ kỹ thuật
  • ↳   Bài viết cũ
  • ↳   Thiết kế Template
  • ↳   Joomla! 1.5
  • ↳   Hỏi đáp Joomla! 4.x
  • ↳   Welsh Forum
  • Other Forums
  • ↳   Open Source Products for Joomla!
  • ↳   The Lounge
  • ↳   Forum Post Assistant (FPA)
  • Joomla! Development Forums
  • Joomla! Official Sites & Infrastructure
  • ↳   docs.joomla.org — Feedback/Information
  • ↳   extensions.joomla.org — Feedback/Information
  • ↳   joomla.com — Feedback/Information
  • ↳   Sites & Infrastructure — Feedback/Information
  • ↳   Archived Boards — All boards closed
  • ↳   Design and Accessibility — Archived
  • ↳   Quality and Testing — Locked and Archived
  • ↳   Joomla! 1.0.x_Q&T
  • ↳   Q&T 1.0.x Resolved
  • ↳   Known Issues
  • ↳   Superseded Issues
  • ↳   Archive
  • ↳   Q&T 1.0.x Resolved — Archived
  • ↳   Known Issues — Archive
  • ↳   Superseded Issues — Archive
  • ↳   Joomla! 3.x Bug Reporting
  • ↳   Third Party Testing for Joomla! 1.5
  • ↳   Q&T 1.5.x Resolved
  • ↳   Joomla! 1.5 BETA
  • ↳   Joomla! 1.5 BETA 2
  • ↳   Reaction to the ‘Letter to the community’
  • ↳   Reaction to New Project Name
  • ↳   Logo Competition
  • ↳   Humor, Fun and Games
  • ↳   Libraries
  • ↳   patTemplate
  • ↳   com_connector — Multi Joomla Bridge
  • ↳   CiviCRM Support
  • ↳   CiviCRM Installation Issues
  • ↳   FAQ Archive
  • ↳   FAQ Discussion Board
  • ↳   3rd Party Extensions FAQ
  • ↳   FAQs not moved
  • ↳   3rd Party/Non Joomla! Security FAQ
  • ↳   Joomla! Coding 101
  • ↳   Joombie Tools of the Trade
  • ↳   Joombie Coding Q/A
  • ↳   Joombie Think Tank
  • ↳   Joombie Developer Lab
  • ↳   Joomla Forge — Archived
  • ↳   Non-Profit Organizations and Joomla!
  • ↳   Schools and Universities
  • ↳   Bangsamoro Forum
  • ↳   Joomla! 1.5 Template Contest
  • ↳   SMF — Simplemachines.org Forum
  • ↳   GPL Discussion
  • ↳   Security Announcements — Old
  • ↳   Tips & Tricks — Moving
  • ↳   Submit Your Suggested Tips & Tricks to Docs.joomla.org now please.
  • ↳   Google Summer of Code and GHOP
  • ↳   Google Summer of Code 2008
  • ↳   Proposed projects
  • ↳   Student area
  • ↳   Past Google Summer of Code Editions
  • ↳   Google’s Highly Open Participation Contest
  • ↳   Documentation
  • ↳   Suggestions, Modifications, and Corrections
  • ↳   Archive
  • ↳   1.5 Archive
  • ↳   Suggestions, Modifications & Corrections
  • ↳   Submit
  • ↳   Feedback and Suggestions
  • ↳   Applications for participation in the Development Workgroup
  • ↳   Development
  • ↳   1.5 Site Showcase — Archived
  • ↳   1.0 x Site Showcase — Archived.
  • ↳   Feature Requests — White Papers — Archived
  • ↳   Under Review — Archived
  • ↳   Accepted — Archived
  • ↳   Not Accepted — Archived
  • ↳   Wishlists and Feature Requests — Archive
  • ↳   Wishlist Archives — Archived
  • ↳   Spanish Forum — Archive
  • ↳   Papelera
  • ↳   Tutoriales
  • ↳   General
  • ↳   Salón de la Joomlaesfera hispanohablante
  • ↳   Danish Forum — Archive
  • ↳   Diskussion af Meddelelser + Sikkerhedsmeddelelser + FAQ
  • ↳   Shop.Joomla.org
  • ↳   Joomla! 1.6 RC Support [closed]
  • ↳   Joomla! 1.0 Coding
  • ↳   Core Hacks and Patches
  • ↳   Joomla! 2.5 Beta Support
  • ↳   People.joomla.org — Feedback/Information
  • ↳   Joomla! 1.5 Bug Reporting
  • ↳   Joomla! 1.5 Coding
  • ↳   Joomla! 3 Beta Support
  • ↳   Trending Topics
  • ↳   Help wanted in the community
  • ↳   templates.joomla.org — Feedback/Information
  • ↳   Certification
  • ↳   Albanian Forum
  • ↳   Azeri Forum
  • ↳   Urdu Forum
  • ↳   Basque Forum
  • ↳   Itzulpenaren inguruan
  • ↳   Laguntza teknikoa
  • ↳   Belarusian Forum
  • ↳   Maltese Forum
  • ↳   Hungarian Forum
  • ↳   Slovenian Forum
  • ↳   Japanese Forum
  • ↳   Khmer Forum
  • ↳   ពិពណ៌​ស្ថាន​បណ្ដាញ​ជុំឡា
  • ↳   ជុំឡា​ខ្មែរ​មូលដ្ឋានីយកម្ម
  • ↳   Community Blog Discussions
  • ↳   JoomlaCode.org
  • ↳   Joomla! Marketing and PR Team
  • ↳   resources.joomla.org — Feedback/Information
  • ↳   Training.Joomla.org
  • ↳   OpenSourceMatters.org
  • ↳   magazine.joomla.org — Feedback/Information
  • ↳   Site Showcase
  • ↳   Joomla! 4 Related
  • ↳   Joomla! Events
  • ↳   Joomla! Ideas Forum
  • ↳   Registered Joomla! User Groups
  • ↳   Joomla! 2.5 Coding
  • ↳   Joomla! 2.5 Bug Reporting
  • ↳   User eXperience (UX)
  • ↳   Joomla! Working Groups
  • ↳   Translations

In my last question I tried to modify mod_latest_articles module, and added myCustomFunction to ArticlesLatestHelper.php like this :

/**
 * @package     Joomla.Site
 * @subpackage  mod_articles_latest
 *
 * @copyright   Copyright (C) 2005 - 2019 Open Source Matters, Inc. All rights reserved.
 * @license     GNU General Public License version 2 or later; see LICENSE.txt
 */

namespace JoomlaModuleArticlesLatestSiteHelper;

defined('_JEXEC') or die;

use JoomlaCMSAccessAccess;
use JoomlaCMSComponentComponentHelper;
use JoomlaCMSFactory;
use JoomlaCMSRouterRoute;
use JoomlaComponentContentSiteModelArticlesModel;
use JoomlaRegistryRegistry;
use JoomlaUtilitiesArrayHelper;

JLoader::register('ContentHelperRoute', JPATH_SITE . '/components/com_content/helpers/route.php');

/**
 * Helper for mod_articles_latest
 *
 * @since  1.6
 */
abstract class ArticlesLatestHelper
{
    /**
     * Retrieve a list of article
     *
     * @param   Registry       $params  The module parameters.
     * @param   ArticlesModel  $model   The model.
     *
     * @return  mixed
     *
     * @since   1.6
     */
    public static function getList(Registry $params, ArticlesModel $model)
    { // this is the built-in function ... }


    public static function myCustomFunction($created_date)
    {
        $date = new JDate($created_date);
        echo $date->format('l, d F Y H:i', false, false);
    }   

I’m able to call the function from the default.php by using @Zollie’s solution, but now I got this error message when using JDate inside my function

Error: Class ‘JoomlaModuleArticlesLatestSiteHelperJDate’ not found: Class ‘JoomlaModuleArticlesLatestSiteHelperJDate’ not found

Can anybody tell me, what am I doing wrong in here now? Thanks!

mickmackusa's user avatar

mickmackusa

4,5434 gold badges15 silver badges45 bronze badges

asked May 6, 2019 at 23:10

webchun's user avatar

2

I’m answering the question because it is obviously not a Joomla 4 core bug but a mistake in the developer’s coding and the problem would be the same in Joomla 3 too.

If you try to use a Joomla core class in your code you have to include that class on the top of the file otherwise Joomla does not know what it needs to use, so:

use JoomlaCMSDateDate;

Then you can use in your code:

$date = new Date($created_date);

These classes are not automatically available everywhere across Joomla unless you point to them. So include the classes you use on the top of your files.

answered May 7, 2019 at 4:25

Zollie's user avatar

ZollieZollie

2,4561 gold badge7 silver badges22 bronze badges

5

День X настал и в административной панели Joomla появилось сообщение о том, что поддержка Joomla 3 прекращается. Есть тысяча причин задуматься о переходе на новую версию. И имя ей — Joomla 4. К моменту написания этих строчек я уже перенес несколько сайтов и хочу поделиться своими мыслями о том, как происходила данная операция, какие подводные камни ждут на пути обновления движка вашего сайта.

Если к моменту перехода на Joomla 4 вы исправно обновляли движок своего сайта, который по научному называется системой управления контентом (CMS), то база данных вашего сайта находится в необходимом для обновления состояния. И это хорошая новость.

Ибо знал я те времена, когда при переходе с одной версии на другую для переноса данных приходилось использовать сторонние компоненты.

На этом хорошие новости заканчиваются.

Все последующие препятствия, загадки и всевозможные квесты будут связаны со скриптами. И это неудивительно. В Joomla 4 серьезно переработано сердце системы, удалены либо переименованы некоторые классы и методы.

Поэтому при попытке открыть компонент, модуль или плагин разработанный под старые версии Joomla вас будет приветствовать сообщение об ошибке.

Мой вердикт таков: если вы не обладаете навыками программирования на PHP, шансы успешно обновить Joomla стремятся к нулю. Ибо весь процесс переноса — это адаптация уже установленных расширений к новой версии.

А теперь минутка рекламы.

Если вы не готовы самостоятельно осуществить процесс миграции c Joomla 3 на Joomla 4 — пишите и звоните. Мой телефон (он же телеграмм и WhatsUP) указан на сайте. Я оказываю данную услугу.

В моем понимании миграция сайта — это:

1) Сохранение дизайна «старой версии» сайта

2) Сохранение функциональности сайта

3) Отсутствие ошибок после обновления сайта, как на его страницах, так и в консоли браузера

Для посетителя сайта процесс обновления должен пройти незаметно, однако администратор получает новую версию Joomla и в качестве приза — возможность регулярного обновления этой системы.

В начале непростого пути под названием «Обновление Joomla» хочу сделать объявление!

Если вы планируете производить миграцию на рабочем сайте, немедленно откажитесь от этой идеи!

Для обновления сайта необходимо создать полную копию сайта: и файлы и база данных никак не должны пересекаться с его рабочим вариантом.

Пока мы производим миграцию на тестовом, оригинальный сайт продолжает работать. После завершения миграции мы просто заменяем один сайт другим!

Итак, мы в административной панели нашего подопытного сайта. Который работает под управлением Joomla 3.

Перед началом обновления, обязательно нужно отключить все сторонние плагины и модули. То есть те плагины и модули, которые не входили в стандартную сборку Joomla.

Особенно внимание нужно уделить системным плагинам и модулям административной панели. Ибо с большой вероятностью они приведут к 500 ошибке на этапе завершения обновления системы и административная панель Joomla будет недоступна.

Операцию по обновлению Joomla мы начинаем в одноименном компоненте.

При открытии страницы компонента «Обновление Joomla» есть большая вероятность того, что вы увидите сообщение о том, что обновления отсутствуют.

Не верьте не единому слову!

Для устранения этого недоразумения в правом верхнем углу нажмем кнопку «Настройки»

Далее в качестве сервера обновлений выбираем «Joomla Next»

Сохраняем настройки и возвращаемся на страницу компонента обновления. Откроется страница, где будет показана актуальная версия для обновления.

Также будет произведен анализ вашей системы и красным цветом подсвечены плагины, которые требуется отключить.

На самом деле… а я писал об этом выше… мы должны выключить все плагины, которые не входят в стандартную сборку Joomla, поэтому подсвеченных красным цветом расширений у нас не будет. А если они вдруг, каким то магическим способом, обнаружились, немедленно отправляемся их отключать.

Заключительный шаг — переход на вкладку «Автоматическое обновление» и нажатие на кнопку «Установить»

Упс… ошибка 500

Достаточно распространенная ситуация, когда обновление завершается страницей с ошибкой. Я не поленился и выложил скриншот такой страницы.

Зачем?

Потому что она красивая.

А еще она не несет никакой информации. И с этим нужно что-то делать.

Из великого администратора Joomla придется переквалифицироваться в не менее великого детектива, потому что все последующие шаги будут состоять из многочисленных расследований происходящего.

При любой ошибке на сайте, задача номер один — найти скрипт приводящий к ошибке, задача номер два — устранить ошибку.

Для решения первой задачи нам понадобится включить режим отладки. Обычно это делается из административной панели, однако она у нас недоступна.

Поэтому в корневой директории нашего сайта находим файл configuration.php. Для этого понадобится FTP менеджер с возможностью редактирования.

Открываем файл в текстовом редакторе и находим строку:

public $debug = ‘0’;

…меняем значение на 1, чтобы получилось:

public $debug = ‘1’;

Сохраняем файл configuration.php, возвращаемся в административную панель и обновляем страницу с ошибкой.

На этот раз она будет не настолько красочной, как ранее, зато гораздо информативнее. Пример такой страницы привожу ниже, где стрелочками пометил места, которые представляют ценность и важность.

Если вам удалось решить проблему с ошибкой и административная панель стала доступна для полноценной работы (а может, и вовсе не было никакой ошибки), следует провести ревизию установленных сторонних расширений: компонентов, модулей, плагинов и поискать их версии для Joomla 4 на сайтах разработчиков.

Вполне может быть, что все необходимые комплектующие найдутся и это будет очень хорошо, поскольку избавит от самостоятельной переделки и миграции компонентов под Joomla 4.

Проблемы могут создавать не только сторонние расширения, но и те, что идут в стандартной поставке Joomla.

А именно переопределения макетов шаблона, который работал под Joomla 3 и который мы должны переделать под Joomla 4.

Пару слов о том, как переделать шаблон под Joomla 4

Условно шаблоны для Joomla можно поделить на две категории:

1) Те, что созданы на основе фреймворков — дополнительных плагинов, компонентов

2) Те, что созданы без фреймворков

В первом случае нужно немедленно идти на сайт разработчика фреймворка и искать версию для Joomla 4.

Если таковой нет, то придется либо переписывать фреймворк самому, что очень трудозатратно. Либо искать другой шаблон.

К слову, я всегда был противником варианта номер один.

С шаблонами созданными стандартными средствами Joomla — проще. Однако, есть нюансы.

В Joomla 4 не отображаются заголовки у модулей

Одним из таких нюансов может быть исчезновение заголовков у модулей после обновления сайта и перехода на Joomla 4.

Как решить эту проблему?

Предлагаю открыть файл index.php нашего шаблона и изучить фрагмент кода, который выводит любой из модулей.

В моем случае код отвечающий за вывод модуля в позиции «HEADER-A» выглядит так:

<jdoc:include type=»modules» name=»header-a» style=»vmBasic»/>

Обратите внимание на аттрибут STYLE.

Его значение: vmBasic.

Данный параметр говорит системе: отобрази данный модуль с помощью макета «vmBasic».

И если система не находит такой макет, то выводит модуль с помощью макета по умолчания, где заголовок не отображается.

В Joomla 3 макеты определялись в файле, расположенном в каталоге:

/templates/ваш_шаблон/html/modules.php

Где каждому макету соответствовала отдельная функция.

В Jooomla 4 за определение стиля модуля отвечает отдельный файл. Располагаться он должен в каталоге:

templates/ваш_шаблон/html/layouts/chromes/имя стиля.php

Как устроен файл стиля модуля можно посмотреть в предустановленном шаблоне «Cassiopeia», который поставляется с Joomla 4.

Ошибки после обновления

behavior::modal not found или behavior::formvalidation not found.

Достаточно частая ошибка, которая вызывается устаревшими макетами модулей и компонентов. Для ее устранения нужно при включенном режиме отладки выяснить: какой файл ее вызывал, далее найти в файле инструкцию:

JHTML::_ (‘behavior.modal’);

или

JHtml::_(‘behavior.formvalidation’);

И стереть ее.

Последнюю неплохо заменить на следующую конструкцию:

use JoomlaCMSHTMLHTMLHelper; 
use JoomlaCMSFactory;

$app = Factory::getApplication(); 
$document = $app->getDocument();

$wa = $document->getWebAssetManager();
$wa->useScript('keepalive') ->useScript('form.validate');
HTMLHelper::_('bootstrap.tooltip');

Она необходима для корректной работы форм, а именно проверки полей на корректность заполнения

К слову, необходимо везде отказываться от класса Jhtml и заменять его классом HTMLHelper. Не забывая его импортировать в начале файла.

Cannot access protected property JoomlaCMSMenuMenuItem::$params

Ошибка возникает при обращении к свойству PARAMS, которое в Joomla 4 имеет уровень доступа «protected», что запрещает прямое к нему обращение.

Там, где появляется подобная ошибка команду

$ваша переменная->params->get

Нужно заменить на:

$ваша переменная->getParams()->get

Class ‘JRequest’ not found

От класса Jrequest по хорошему нужно было отказываться еще в Joomla 3. поскольку он в даже в третьей версии считался устаревшим.

В Joomla 4 волевым усилием разработчики вообще его исключили.

Если вы видите в коде нечто вроде:

Jrequest::getVar(‘какая то переменная’)

То перед вызовом метода необходимо получить объект input, в котором хранятся все переменные запросов:

use JoomlaCMSFactory;
$app = Factory::getApplication();
$input = $app->input; 

Далее там, где было

Jrequest::какой то метод(какая то переменная)

мы меняем на :

$input->get('какая то переменная’)

На тему работы с переменными запроса есть хорошая статья. Она написана до выхода Joomla 4, но до сих пор актуальна.

Нюанс лишь в том, что класс JFactory в Joomla 4 заменен на Factory

Class ‘JApplication’ not found

Класс JApplication также был удален, однако наша задача не заменить этот класс целиком, а понять — к каким методам обращался «старый» код из этого класса.

И делаем мы это также из режима отладки.

Как видим, ошибка в файле /administrator/components/com_k2/models/item.php, на 931 строке.

И если мы откроем этот фрагмент кода, то увидим обращение к методу getHash

Выглядит это так:

JApplication::getHash 

Данный метод получает хеш, попросту кодирует определенные данные. В Joomla 4 его можно заменить следущей конструкцией:

use JoomlaCMSApplicationApplicationHelper;
ApplicationHelper::getHash($Ваша_переменная);

При миграции компонентов с Joomla 3 на Joomla 4 ошибку связанную с классом  JApplication можно встретить и в административной панели.

В частности, в Joomla 3 существовал метод JApplication::stringURLSafe, который использовался при создании алиасов материалов.

В Joomla 4 заменой этому методу станет: ApplicationHelper::stringURLSafe

Заключение

Пишу эти строчки 15 августа 2022 года. Уверен, данный материал будет неоднократно обновляться. Хочется сказать лишь одно: универсального рецепта по переносу сайта с Joomla 3 на Joomla 4 нет. При этом нужно понимать, что портировать на новую версию можно и нужно любой сайт. Независимо от установленных на нем расширений и предыдущих их доработок.

С уважением, Владимир Егоров

Don’t worry, you’re not alone! If you have an error that looks something like: “wordwordword not found”, it may be because of an extension you’ve recently installed or updated. Here are two more examples:

Namespaces Error 3[4.0] Class ‘JoomlaComponentTemplatesAdministratorControllerStyle’ not found

Namespaces Error 3An error has occurred. Class ‘JoomlaModuleLoginAdministratorHelperLoginHelper’ not found

Quick Joomla history lesson: when Joomla switched from version 1.5 to version 2.5, there were significant changes, creating what is known as a technology cliff. So many users were completely lost after the change because there was no way for them to upgrade to Joomla 2.5 without help. Joomla wants to prevent that from happening again, while still having the flexibility to make important and necessary upgrades to make Joomla even more powerful and versatile.

In version 4.0, Joomla is using something called namespaces, which is a newer technique in PHP, so extensions built for 4.0 may cause issues if you’re still using Joomla 3.8 or earlier.

In order to facilitate a smoother transition this time, Joomla made version 3.9 a bridge between Joomla 3.x and Joomla 4. Joomla 3.9 is compatible with everything for the earlier 3 series versions, AND it will also work with extensions created for version 4.0. Importantly, in version 4.0, Joomla is using something called namespaces, which is a newer technique in PHP, so extensions built for 4.0 may cause issues if you’re still using Joomla 3.8 or earlier.

Bottom line: if you’re seeing the error above, it’s most likely because you’ve installed or updated an extension that is built for Joomla 4.0, but you haven’t upgraded to the bridge yet (version 3.9).There are two solutions to fix this problem:

1. If you can still access the backend of the website, upgrade to Joomla 3.9. Once you’ve done that, you’ll be able to continue using extensions built for earlier versions, but you’ll also be able to use extensions that have already been adapted for Joomla 4.0. *Important note: please ensure you back up before you upgrade!

2. If you cannot access the backend, manually disable the extension directly in the database using phpmyadmin. Here is a quick tutorial of how to do that.

Don’t have time to do this yourself and just want it fixed quickly? No problem! Contact us today, and we’ll take care of it for you.

I Need 9-1-1 Help Learn about Website Oil Changes

Comments

@frogydiak

@joomla-cms-bot
joomla-cms-bot

changed the title
[4.0-dev] Front End Error

[4.0] Front End Error ‘JoomlaModuleMenuSiteHelperMenuHelper’ not found

Jul 19, 2018

wilsonge

added a commit
that referenced
this issue

Aug 12, 2018

@wilsonge

proman24

added a commit
to proman24/joomla-cms
that referenced
this issue

Aug 18, 2018

@proman24

@kasvith

* [4.0] Pagination [a11y] admin (joomla#21293)

* [4.0] Pagination [a11y]

* Update default.php

* Update modal.php

* Update modal.php

* Update default.php

* Update default.php

* Update default.php

* Update default.php

* Update default.php

* Update default.php

* Update default.php

* Update default.php

* Update default.php

* Update default.php

* Update default.php

* tabs

* Remove registering form paths for paths that no longer exist (joomla#21279)

* Remove random number from code comment

* [4.0] Separate sources from the distributable assets (joomla#21328)

* I like to move it, move it 🕺

* Fix overflow of submenu despite being closed (joomla#21316)

* [4.0] Fixed the translation of the view type in menuitem (joomla#21324)

* Fixed the path  to the XML-File of a layout in a view of a component.

* Add the path to layout schema for Joomla! 3 component

* fixed coding standard

* fixed more coding standard

* fixed the path to layout shema for old Joomla! version

* Codestyle

* 4.0 check for valid session before messing with ini (joomla#21337)

* Added checks for an active PHP session before trying to change ini values.

* Revert "Added checks for an active PHP session before trying to change ini values."

This reverts commit 54aab95.

* Added checks for an active PHP session before trying to change ini values.

* Changed check to isActive() as suggested by @wilsonge .

* Remove tabs/blank line (joomla#21346)

* Update the cli nom commands (joomla#21350)

* Ooops

* Update package.json

* Update compile-es6.js

* remove the automated part here

* Adjusted the batch-language.js to hide the batch move/copy options by default. (joomla#21340)

* [4.0] Article batch operation fixes (joomla#21325)

* some changes in ArticleModel

* Undefined class warnings resolved

* Commented out code removed

* few style changes

* few more style changes

* Removed the function which caused an error because it wasn't declared anywhere

* [4.0] Improving menu item workflow (joomla#21357)

* created new branch

* formatted code

* fixed modal id variable
loaded language file for modal title

* formatted code and ajusted comments

* fixed javascript error due to modal not closing

* code style

* code style

* Codestyle

* [4.0] CSS codestyle offline.css (joomla#21379)

* Sans Serif to sans-serif + newline

* cs

* New version of Joomla

* [4.0] update the custom elements (joomla#21204)

* update joomla-custom-elements + polyfills

* REMOVE

* [4.0] Fixed the parent item dropdown (joomla#21348)

* Fixed the parent item dropdown

* fixed code style

* Fix 2nd level menu (atum template) not showing (joomla#21367)

* fixed button description to language string (joomla#21387)

* [4.0] RTL frontend login (joomla#21402)

* [4.0] Fix joomla#21357 when multilanguage is implemented (joomla#21391)

* [4.0] Fix: Associations tab should display only one Notice when item
edited is set to ALL languages

* correcting my local branch

* [4.0] Fix 21357 when multilang is implemented

* [4.0] ES6 conversion of select-colour.js (joomla#21406)

* select-colour

* make sure we always compare numbers

* correction: event name

* [40] ES6 batch language script and move it to the right place (joomla#21405)

* batch language

* correction: event name

* [4.0] Accessing property without checking the object state causing Joomla installer non-responsive (joomla#21413)

* Bug fix for joomla#21412

After installing Joomla, go to customization and select language say Hindi for installation. If the language cannot be installed, the server will not return any value, and the value is null. But the below code is accessing its properties without checking the data is null or not.

* Update LanguagesModel.php

* Remove extra space

* Remove extra tabs

* [4.0] ES6 multiselect.js (joomla#21409)

* multiselect

* hound

* this needs to be in a higher element

* drop this

* [4.0] Simplifying lang load (joomla#21415)

* [4.0] Update readme.md (joomla#21392)

Remove reference to jenkins

* es6 please (joomla#21341)

* Better error message for MySQL 8 workaround (joomla#21339)

* Better error message for MySQL 8 workaround

* change error message

* error message typo in en-US

* Fix typo in en-GB

* [4.0] DRY for warning pages (joomla#21331)

* DRY

* Update package.json

* Update restore_finalisation.php (joomla#21332)

* [4.0] [a11y] Pagination site (joomla#21306)

* [4.0] [a11y] Pagination

* drone

* cs

* template css etc

* woof woof

* jtext

* correct scss to highlight current

* hound

* fix link styles

* hound

* conflicts

* revert joomla#18533 and move back to the stable state (joomla#18558)

* [4.0] ES6 please, validate.js (joomla#21417)

* validate

* missing class

* [4.0] Fix: Associations tab should display only one Notice when item edited is set to ALL languages (joomla#21362)

* [4.0] Fix: Associations tab should display only one Notice when item
edited is set to ALL languages

* correcting my local branch

* [4.0] Fix: Associations tab should display only one Notice when item
edited is set to ALL languages

* [4.0]namespace administrator components com_languages (joomla#21058)

* com_languages

* Update edit.php

* Update StringsModel.php

* Update OverridesModel.php

* [4.0]namespace administrator components com_installer (joomla#21056)

* com_installer

* Update InstallModel.php

* Update UpdateModel.php

* jupdatecheck (joomla#21421)

* bug in the regex (joomla#21427)

* [4.0] Split the configuration of the session service on a per-application basis, restructure session GC command (joomla#19594)

* Split the configuration of the session service on a per-application basis, restructure session GC command

* Make a session factory, move handler creation into it

* Expand comments on session service key aliasing

* Apparently this is our PHPCS style?

* Change to a less than readable variant of the signature because our PHPCS rules suck

* Fix container reference

* PHPCS fixes

* Inject Session class options into factory, validate option presence

* [4.0] Cleanup error handling in the installer on failed DB Connections (joomla#20334)

* Cleanup of messages in installation error cases

* Implement feedback

* Code cleanup

* Remove invalid character from cache namespace declaration

* com_wrapper ES6 (joomla#21430)

* Fix namespace code style of com_admin

* Fix namespace code style of com_associations

* [4.0] ES6 com_tags (joomla#21432)

* com_tags

* mute the dog

* [4.0] ES6 com_languages overrider (joomla#21434)

* overrider

* woof

* grrr

* [4.0] ES6 please, tinyMCE (joomla#21428)

* tinyMCE

* mute the dog

* remove the es5 files

* No console errors on the BS and tiny sourcemaps

* [4.0] ES6 please, sampledata.js (joomla#21422)

* sampledata

* mute the dog

* [4.0] Change com_cpanel to services (joomla#21419)

* Change com_cpanel to services

* dispatcher

* fields (joomla#21440)

* [4.0] ES6 please, com newsfeed (joomla#21433)

* com_newsfeed

* woof

* woof ?

* [4.0] Install discover 500 (joomla#21443)

Wrong namespace change - my bad

* com_mailTo (joomla#21442)

* [4.0] ES6 please, com_finder (joomla#21438)

* finder

* hound

* These were supposed to be ES6

* woof

* [4.0] Update build.js (joomla#21446)

The installation template was missing from the watch and build scrippts

* [4.0]Archive view (joomla#21449)

Fix the missing endif to the title

* Change content history to services (joomla#21418)

* use the class keyword

* plg_stats (joomla#21455)

* [4.0] ES6 please, com_contacts (joomla#21453)

* com_contacts

* cleanup

* [4.0] ES6 Please com_contenthistory (joomla#21454)

* history

* woof

* Installer library - use parameterized queries (joomla#21459)

* [4.0] Installer library qn/q (joomla#21461)

Change the usage of q and qn to quote and quoteName in this recently merged code

* [4.0] ES6 please: core+keepLive (joomla#21404)

* core+keepLive

* Ooops, missing things here

* CS

* fixes

* [4.0] Password eye button (joomla#21462)

Changed the class in the layout and the js

* [4.0] ES6 please,  com media edit (joomla#21444)

* media edit

* edit

* woof

* oops

* hmm

* really?

* [4.0] Admin Pagination [a11y] (joomla#21424)

* [4.0] Admin Pagination [a11y]

Similar to joomla#21306 but for the admin

The aim of this PR is to make the pagination seen in list views in the front end accessible - there are no visual changes

- Wrap the pagination in a nav and add a role (needed for IE) and an aria-label
- Ensure font icons have aria-hidden=true
- Add aria-current to the selected page
- Add aria-title to the active links eg Go to page 1

Note 1
that the disabled links will not be announced to a screen reader which is the intended behaviour

Note 2
the list is an unordered list which appears to be the standard as otherwise the links would be announced as Link 1 go to page 2 etc which is nonsense

### Changes
**administratortemplatesatumhtmlpagination.php**
removed - we dont need an override

**layoutsjoomlapaginationlinks.php**
Made similar to list and set showlimitbox to false (looks like legacy code to me)

** administratortemplatesatumscssblocks_layout.css
new file with just the styling used in the front end

### Testing

Should be testable with patchtester but make sure that the template override has been deleted

* cs

* update joomla-browser [CLEAR CACHE]

* move rebuild cache step before the tests

* [4.0] ES6 please, com menu (joomla#21463)

* com_menus

* woof

* Check that custom session path exists, create if not, if can't create then use default (joomla#19431)

* Destroy session on deleting installation folder (joomla#20426)

* xml codestyle

* [a11y] Joomla logo is a decorative image only so should not have an alt description

* Remove duplicate system-message-container div - important so we have unique id

* fonrawesome is include in the template.css by the sccs - no need to load it again

* update code comment it is super user not supr admin etc

* use quote and quotename not q and qn

* namespace - JText

* Namespace JHtml

* Help Docs link - add a link to the docs site and meaningful text for screenreaders to the "lightbulb" [a11y]

* change section role=main to just <main>

* [a11y] Add h1 to the page

* You can not use a custom element to display the noscript message - obviously that's not going to work because the custom element is javascript - inception

* [a11y] Move message about installing languages to be a caption
[a11y] add scope to languages table

* [a11y] contrast on language version number

* [a11y] Section headings not nested correctly h1->h3 now h1->h2

* Namespace JFile

* Namespace Jfolder

* target blank on mysql8 link to docs

* [a11y] footer link color and hover fixes joomla#21359

* Validate name of database fixes joomla#15583

* remove all references to switcher - not being used and it breaks scss compile

* template.css after running npm build:css [note this hadn't been run for a while as it was missing from the build scripts]

* forgot to save

* quoteName

* hound

* missing semicolon in original code

* aria-hidden

* quote issue reported by @Quy

* aria-hidden

* fix regex - thank @ggppdk

* regex again

* [4.0] Remove Exception-catching from JMail (joomla#21320)

* Updated the Mail.php file to the changes in PR joomla#12179

* Added Exception Handling for the Mails that get send after sending private messages in the Backend

* Update Mass-Mail Function to handle the Exceptions from the JMail class

* Update the update notification plugin to handle the new Exceptions from the JMail class

* Update the Contact-Module to handle the exceptions thrown by the JMail class

* Update joomla.php
When you create a user and the creation email cant be sent, the thrown exception from the JMail class is handled

* Update DisplayController.php
When you try to forward an article via email and it fails the exception os caught and handled

* Update RemindModel.php
When you try to send a reminder email because you forgot your username and the mail can not be sent the exception is caught and handled.

* Update ResetModel.php
When you try to send a reset email because you forgot your password and the mail can not be sent the exception is caught and handled.

* Update RegistrationModel.php
When you try to try to register a new User account in the frontend, and the registration-mail can not be sent the exception is caught and handled.

* Updated multiple files to better handle the new exceptions thrown by the JMail class and still display the correct messages.

* Updated MessageModel.php to better handle the Exceptions thrown in the JMail class.
Added new Error Message to translation file.

* Removed unnecessary redirect from DisplayController.php

* Improved Exception handling in the joomla.php that is used when creating users in the backend.

* Updated translation file

* Fixed a code-style issue

* fixed a twice used class

* [4.0] Feature/New Publishing Workflow (joomla#20381)

Thanks @bembelimen @Didldu-Florian @puneet0191 @priiish @brianteeman and @chmst

* [4.0] Constant usage (joomla#18504)

* CONSTANT usage

* Revert change in one case, as it might be useful to have the extra info there.

* U Can't Touch This!

* Fix conflicts and remove some replacements due to possible b/c break

* By default categories use the default workflow

* [4.0] [a11y] com_users icons (joomla#21468)

While testing joomla#21441 (which is not related to this pr) I spotted that we missed three icons that should have aria-hidden applied to them

The three icons can be seen in the admin when listing users

-  icon to add a note for the user.
-  icon to filter the notes list. You will need to create some notes first
-  number of notes for the user. You will need to create some notes first

* [4.0] ES6 please, com modules (joomla#21465)

* com_modules

* woof

* [4.0] ES6 please, searchtools (joomla#21467)

* searchtools

* haha

* Fix namespace code style of com_banners

* Fix namespace code style of com_cache

* Fix namespace code style of com_categories

* Fix namespace code style of com_checkin

* Fix namespace code style of com_config

* Fix namespace code style of com_contact

* Fix namespace code style of com_content

* Fix namespace code style of com_contenthistory

* Fix namespace code style of com_cpanel

* Fix namespace code style of com_csp

* Fix namespace code style of com_fields

* [4.0] workflow namespace (joomla#21471)

* [4.0] workflow namepsace

Quick pr to namespaace jtext and jtml

* oops

* [4.0] Workflows - fix xml codestyle (joomla#21470)

fix various codestyle issues

* Add missing doc block

* [4.0] MVC mot Mvc (joomla#21478)

* [4.0] MVC mot Mvc

Codestyle

* oops

* [4.0] Workflow - too (joomla#21480)

* [4.0] Workflow - too many

In english it is "too many" when you refer to more than. You use "to" when you refer to travelling from A to B

* Revert "[4.0] Workflow - too many"

This reverts commit cd2058e.

* too many

* [4.0] Use the new hasField() in JTable  (joomla#21479)

* [4.0]  Move JTable property_exists to hasField method 

Move JTable property_exists to hasField method

* asset table

* CoreContent

* Extension

* Nested

* [4.0] Workflow namespace 2 (joomla#21484)

* jroute

* Jsession

* jfactory

* Jlayouthelper

* jtext

* Bump Composer dependencies (joomla#21490)

* [4.0] Workflow [a11y] (joomla#21488)

Remove th and scope=col from the checkall cell
Add th and scope=row to the title cell

* [4.0] Installer - precheck css (joomla#21482)

* [4.0] Installer - precheck css

PR for joomla#20773

### Before

### After

### Testing
You will probably need to force an error on your system or to edit the file
installationsrcModelChecksModel.php
and change some of the lines with

option->state
to
$option->state  = count($available);

* woof

* [4.0] Workflow unused variable (joomla#21486)

Remove unused variable - probably remnant from removing the tfoot

* [4.0] Workflows commented (joomla#21483)

Remove 1 block of commented out code
Expose 1 block of commented out code

* [4.0] Workflow remove copy/paste code (joomla#21489)

Can only assume that this id is from some other code that was copy pasted here without thought as it makes no sense to have this id

* Fix namespace imports in workflow Controller

* Codestyle fix

* [4.0] Workflows language (joomla#21493)

* [4.0] Workflows language

en-gb and codestyle

* oops

* Remove unused import

* Fix namespace

* [4.0] Use the new hasField()  (joomla#21494)

* [4.0] Use the new hasField()

* use the new hasField()

* use the new hasField()

* Codestyle and use whereIn from db driver

* [4.0] c/p error in com_installer namespace commit (joomla#21492)

JVERSION is a string for translation.

* I need to setup my IDE

* Array -> integer

* Use namespaced class

* Cleanup return type

* Fix code comments

* use function not property

* Fix docblocks

* [4.0] Fix npm script on windows (joomla#21505)

* Fix compile-es6 script on Windows machines.

* Adding back .min.js

* [4.0] Fix workflow state submenu (joomla#21508)

* Fix redirect for state checkin

* Clean up

* Fix broken multilingual handling (joomla#21512)

* Fix workflows.xml (joomla#21511)

* Fix namespace code style of com_finder

* Fix namespace code style of com_installer

* Fix namespace code style of com_joomlaupdate

* Fix namespace code style of com_languages

* Fix namespace code style of com_login

* Fix namespace code style of com_menus

* Fix namespace code style of com_messages

* Fix namespace code style of com_modules

* Fix namespace code style of com_newsfeeds

* Fix namespace code style of com_plugins

* Fix namespace code style of com_postinstall

* Fix namespace code style of com_redirect

* Fix namespace code style of com_search

* Fix namespace code style of com_tags

* Fix namespace code style of com_templates

* Fix namespace code style of com_users

* com_templates ES6 (joomla#21431)

* Merge artcle title, alias, category to one column (joomla#21503)

* [WIP][4.0] - workwflow mysql schema (joomla#21499)

* [4.0] - workwflow mysql schema [wip]

* extension field consistent

make the extension field consistent with the current schema  ie varchar(50)

* Fix joomla#21517

* Namespaced class/docblock

* Codestyle

* Improve docblocks

* Use namespaced code

* Use namespaced table class

* use a newer version of joomla-browser with higer timeout

* [4.0] Fields redo, switcher (joomla#21227)

* do not recreate child elements on node move

* Change span to fieldset to properly adapt focus

* label for sould targeting the fieldset

* one more try

* again

* aria-labeledby

* Remove wrongly committed file

* [4.0] layout missing from joomla#21424 (joomla#21561)

* [4.0] layout missing from joomla#21424

* hound

* [4.0] State to stage (joomla#21544)

* Change "state" to "stage"

* article-model

* Change "state" to "stage"

* Spelling correction controler/controller

* Fix typos

* Revert renaming of workflowstate

* Revert renaming of workflowstate

* Fix Language-key and String, rename the e-mail param, revert change of the classname

* Fix typos

* Some more state-stage changes

* Email without hyphen

* Language string copied

* Fix errors in renaming state to stage for workflow (joomla#21563)

* Fix errors in renaming state to stage for workflow

* Fix table

* [4.0] Use the new hasField() (joomla#21496)

* [4.0] Use the new hasField()

* use hasField()

* use the new hasField()

* use the new hasField()

* use hasField()

* oops

* [4.0] FIX searchtools (joomla#21562)

* Clean up and alpha-order imports (joomla#21577)

Signed-off-by: Roland Dalmulder <contact@rolandd.com>

merged with trust in phpstorm

* Add back package lock file missing

* Fix joomla#21177

* [4.0] Revert helper (joomla#21523)

* Remove readded core.js

* Remove outdated ContentHelper::filterText method

* Remove outdated ContentHelper::getContexts method

* Remove outdated ContentHelper::validateSection method

* Update countTagItems

* Readd initial archive condition for further use

* Remove blank lines

* Align "="

* Revert line

* [4.0] Install database name validation (joomla#21583)

Correct the regex on the database name to prevent _ as the first character

* [4.0] Installation error message (joomla#21572)

Make the error messages on field validation red

* [4.0] ES6 please show on (joomla#21568)

* showon

* woof

* 🐶

* Fix joomla#21304

Fix conflicting class import

* Lowercase for consistency

* [4.0] It was a diffenent factory (joomla#21587)

* I was a diffenent factory

* lowercase keyword

* [4.0] Normalise display of searchtools specific fields for menu items (joomla#21581)

and multilingual associations

* added params to the installation script

* update to 4.8.2 remove temp patch (joomla#21588)

* [4.0] State to stage fixes (joomla#21566)

* [4.0] Stage (joomla#21589)

* [4.0] Stage

Quick PR to make the column header "From..." match the column header "To..."
and the associated message

* cs

* [4.0][Workflow] Lowercase Workflowstage JHtml and Field (joomla#21597)

* Rename Workflow_S_tageField

* Rename JHtmlWorkflowStage to JHtmlWorkflowstage

* [4.0] Empty Trash (joomla#21602)

Makes the empty-trash button red just as the delete button is

* [4.0] Workflow copy paste (joomla#21607)

Fix some copy paste errors in the doc blocks

* [4.0] Webcomponent tab.js typo (joomla#21606)

oriendation ==> orientation

* [4.0] Moved style to the CSS file (backend - system template) (joomla#21569)

* Moved style to the CSS file

* Move style to the CSS file

* Removing trailing spaces

Thanks @Quy

* [4.0] [WORKFLOW] Modifying Toolbar constant (joomla#21591)

* [4.0] [a11y] Modal button colour (joomla#21605)

Make sure the secondary button passes the color contrast check

### Before

### After

(Does not need npm to test)

* remove redundant code (joomla#21609)

* [4.0] State to Stage (joomla#21571)

* State to Stage

* Update en-GB.plg_content_joomla.ini

* Update joomla.xml

* Update joomla.php

* [4.0] - Workflow mysql/postgresql schema (joomla#21520)

* [WIP][4.0] - workwflow mysql schema

-idx prefix 
- removed ENUM field type

* postgresql schema update workflow

* fix mysql install 4 workflow

* workflow mysql install review

* now()

* lost hypen

* workflow postgresql schema

* the state alter

* the state alter

* state2stage

* state2stage

* mysql 5.5

* mysql 5.5

* mysql 5.5 consistency

* mysql 5.5 consistency

* missed quote

* remove duplicated tables

* revert state change on #__content

* revert state field change

* revert start field change

* revert start field change

* Self contain webcomponent SCSS (joomla#21615)

* [4.0] Rules (joomla#21616)

Obvious error missing -

Non functional change

* Enable detectDebug in HTMLHelper::webcomponent by default (joomla#21617)

* Fix namespace code style of mod_feed

* Fix namespace code style of mod_logged

* Fix namespace code style of mod_login

* Fix namespace code style of mod_menu

* Fix namespace code style of mod_popular

* Fix namespace code style of mod_version

* Fix namespace code style of com_banners

* Fix namespace code style of com_contact

* Fix namespace code style of com_content

* Fix namespace code style of com_contenthistory

* Fix namespace code style of com_fields

* Fix namespace code style of com_finder

* Fix namespace code style of com_mailto

* Fix namespace code style of com_modules

* Fix namespace code style of com_newsfeeds

* Fix namespace code style of com_search

* Fix namespace code style of com_tags

* Fix namespace code style of com_users

* Fix namespace code style of com_wrapper

* Fix namespace code style of mod_banners

* [4.0] allow jdoc:include type=message to load assets (joomla#21558)

* dry

* allow modules to enqueMessages

* [4.0] - [workflow] fix undefined condition (joomla#21621)

* [4.0] - [workflow] fix undefined condition

* undefined condition

* [4.0][workflow] - undefinded property on modal (joomla#21622)

* Fix the imports in the archive model (joomla#21620)

* [4.0] drop jQuery (joomla#21575)

* Drop jQuery (again 😃)

* typo

* cs

* remove redundant code

* Update default.php

* Update default.php

* Update default.php

* Update default.php

* fix dos (joomla#21627)

* [4.0][workflow] remove workflow from user menu (joomla#21626)

* [4.0][workflow] remove workflow from user menu

* remove content field item from user menu

* [4.0] [a11y] Set login page title (joomla#21603)

* [4.0] [a11y] Set login page title

a11y rules says that every page should have a meaningfu title

This PR adds the title "Administrator Login - sitename" to the title on the login page

* save before commit

* reverse

* composer and npm install

* [4.0] [workflow] - notice on edit plugin (joomla#21623)

* [4.0] [workflow] - notice on edit plugin

* conservative

* don't kill empy lines

* [4.0] com_workflow: Missing Value for "Count States"  - fixes joomla#21634 (joomla#21635)

* [4.0][workflow] - batch change stage (joomla#21625)

* [4.0][worflow] - batch change stage

* stage line 840

* build

Всегда неприятно, когда ломают обратную совместимость. Но это неизбежный виток развития любого программного обеспечения. Joomla 4 не исключение. Нам обещают обновление в один клик с Joomla 3 до Joomla 4, но всегда нужно помнить — это касается только самого ядра и расширений ядра.

Разработчики сторонних расширений Joomla сами должны позаботиться о том, чтобы их расширения продолжали успешно работать на Joomla 4. Полный список изменений доступен в официальном документе, описывающем потенциальную потерю обратной совместимости при переходе на Joomla 4.

Ниже мы приводим изменения, которые необходимо внести в расширение Joomla, чтобы обеспечить совместимость с Joomla 4. Мы рассматриваем наиболее часто встречаемые проблемы при переходе. Список будет по мере возможности дополняться новыми примерами из практики.

Если у вас какой-то конкретный пример решения проблемы при переходе на Joomla 4, то пишите в комментариях, и мы с удовольствием добавим его в список.

JError и JException

Классы JError и JException были удалены. Используйте нативный Exception в случае возникновения ошибки и приложение для показа предупреждений. Совместимо с Joomla 3. Например:

try
{
	$model = $this->getModel();

	$this->state         = $model->getState();
	$this->items         = $model->getItems();
	$this->pagination    = $model->getPagination();

	parent::display($tpl);
}
catch (Exception $e)
{
	JoomlaCMSFactory::getApplication()->enqueueMessage(
		Text::_('COM_EXAMPLE_ERROR_OCCURRED'),
		'error'
	);
}

JEventDispatcher

Класс JEventDispatcher был удалён. Вызов плагинов необходимо делать через приложение. Совместимо с Joomla 3.

PluginHelper::importPlugin('myplugingroup');

JoomlaCMSFactory::getApplication()->triggerEvent();

JFactory::getXml

Удалён метод JFactory::getXml и класс JXMLElement. Вместо него используйте нативный SimpleXMLElement. Совместимо с Joomla 3.

JHtml

Вызовы типа JHtml::_('behavior.formvalidation'); могут не работать и приводить к ошибке. В каких-то случаях вместо JHtml можно использовать класс HTMLHelper (совместимо с Joomla 3), например HTMLHelper::_('behavior.formvalidator');.

Но предпочтение стоит отдавать новому менеджеру ассетов (существует только в Joomla 4):

/** @var JoomlaCMSWebAssetWebAssetManager $wa */
$wa = JoomlaCMSFactory::getApplication()->getDocument()->getWebAssetManager();
$wa->useScript('form.validate')

JRequest

Класс JRequest был удалён, что будет приводить к ошибке:

Class 'JRequest' not found

Вместо него используйте класс Input. Совместимо с Joomla 3. Пример использования:

$input = JoomlaCMSFactory::getApplication()->input;

$id     = $input->getInt('id'); // JRequest::getInt
$option = $input->getWord('option'); // JRequest::getWord
$view   = $input->getCmd('view'); // JRequest::getCmd

В контроллере компонента можно напрямую обращаться к Input через $this->input.

isAdmin() и isSite()

Удалены методы isAdmin() и isSite(), что может приводить к ошибке:

Call to undefined method JoomlaCMSApplicationAdministratorApplication::isAdmin()

Используйте JoomlaCMSFactory::getApplication()->isClient('administrator') и JoomlaCMSFactory::getApplication()->isClient('site') соответственно. Совместимо с Joomla 3.

Mootools

Javascript фреймворк Mootools был полность удалён из Joomla 4. Это может приводить к ошибкам такого вида:

Uncaught TypeError: document.id is not a function
    at Object.Joomla.submitbutton

Решение тут только одно — использовать нативный Javascript. На примере ошибки выше — заменить document.id на document.getElementById.

Переход на Bootstrap 5

В административной части Bootstrap 2 был заменён на Bootstrap 5. Используйте конвертеры для миграции разметки. Правда админку расширения всё равно придётся переверстать с учётом новой панели управления Joomla 4. Не забудьте почитать про Использование Bootstrap в Joomla 4.

В публичной части больше нет привязки к конкретному фреймворку.

My website was running correctly before 2-3 weeks and now it gives me an error like: joomla fatal error class ‘JError’ not found .
when i am typing the URL it shows the following error message…
Fatal error: Class ‘JError’ not found in /home/dcmops/public_html/gu/libraries/joomla/factory.php on line 565

I am even not able to see the admin tab, it also shows the same error.
Can anybody guide me regarding this issue…??

the code @ line 565 is as follows

if ( JError::isError($db) ) {
            header('HTTP/1.1 500 Internal Server Error');
            jexit('Database Error: ' . $db->toString() );
        }

        if ($db->getErrorNum() > 0) {
            JError::raiseError(500 , 'JDatabase::getInstance: Could not connect to database <br />' . 'joomla.library:'.$db->getErrorNum().' - '.$db->getErrorMsg() );
        }

        $db->debug( $debug );
        return $db;

Thanks & Regards,
Rahul

asked Jun 8, 2013 at 6:05

Rahul Singh's user avatar

4

If you are using Joomla 1.5, this will work fine. Otherwise you need to use standard Exceptions.

You can use a common function to handle all Joomla versions automatically.

Ex:

defined('APP_VERSION') or (version_compare(JVERSION,'1.6.0','ge') ? define('APP_VERSION', 2.5) : define('APP_VERSION', 1.5));

public static function throw_error($code, $msg){

  if(APP_VERSION == '1.5'){

    JError::raiseError( $code, $msg);
  }else{

    throw new Exception($msg, $code);
  }
}

Now you can throw exception just like JError.

e.g.

SomeClassName::throw_error(500, 'An exception occurred');

answered Jun 8, 2013 at 10:50

Nagarjun's user avatar

NagarjunNagarjun

2,30618 silver badges27 bronze badges

  1. Offline

    SLWm

    Недавно здесь

    Регистрация:
    13.01.2016
    Сообщения:
    7
    Симпатии:
    0
    Пол:
    Мужской

    Юзверь обновил джумлу, «патамушта вышло новое обновление и нада обновлять»

    теперь не пускает в админку
    Fatal error: Class ‘JError’ not found in /home/host1264615/kprfkh.ru/htdocs/www/administrator/includes/framework.php on line 35

    Весь инет облазил так и не нашел описания что это за ошибка и как ее исправить
    в указанном месте стоит строчка
    JError::$legacy = true;

    Для полного счастья хацкеры чего-то обиделись именно на этот сайт и за три дня было три последовательных взлома с заменой заглавной страницы.

    Ну и до кучи — бекапа нет.
    И меня попросили разобраться с сайтом после новогодних праздников — то есть я в впринципе и не знаю что там было и как…

    ПОдскажите плиз как всё можно исправить)

    ЗЫ
    есть доступ к сайту по фтп

    ЗЗЫ
    Судя по файлу ридми: Joomla 3.3 version

  2. |title|

    Offline

    |title|

    Активист

    Регистрация:
    19.09.2014
    Сообщения:
    105
    Симпатии:
    26
    Пол:
    Мужской

    Код файла /home/host1264615/kprfkh.ru/htdocs/www/administrator/includes/framework.php в студию

  3. Offline

    SLWm

    Недавно здесь

    Регистрация:
    13.01.2016
    Сообщения:
    7
    Симпатии:
    0
    Пол:
    Мужской

    1. * @package     Joomla.Administrator
    2. * @subpackage   Application
    3. * @copyright   Copyright (C) 2005 — 2014 Open Source Matters, Inc. All rights reserved.
    4. * @license     GNU General Public License version 2 or later; see LICENSE.txt
    5. defined(‘_JEXEC’) or die;
    6. @ini_set(‘magic_quotes_runtime’, 0);
    7. @ini_set(‘zend.ze1_compatibility_mode’, ‘0’);
    8. * Installation check, and check on removal of the install directory.
    9. if (!file_exists(JPATH_CONFIGURATION.‘/configuration.php’) || (filesize(JPATH_CONFIGURATION.‘/configuration.php’) < 10) || file_exists(JPATH_INSTALLATION.‘/index.php’)) {
    10.    header(‘Location: ../installation/index.php’);
    11. // Joomla system startup.
    12. require_once JPATH_LIBRARIES.‘/import.php’;
    13. // Force library to be in JError legacy mode
    14. JError::setErrorHandling(E_NOTICE, ‘message’);
    15. JError::setErrorHandling(E_WARNING, ‘message’);
    16. JError::setErrorHandling(E_ERROR, ‘message’, array(‘JError’, ‘customErrorPage’));
    17. // Botstrap the CMS libraries.
    18. require_once JPATH_LIBRARIES.‘/cms.php’;
    19. // Pre-Load configuration.
    20. require_once JPATH_CONFIGURATION.‘/configuration.php’;
    21. // Set the error_reporting
    22. switch ($config->error_reporting)
    23.      error_reporting(E_ERROR | E_WARNING | E_PARSE);
    24.      ini_set(‘display_errors’, 1);
    25.      ini_set(‘display_errors’, 1);
    26.      ini_set(‘display_errors’, 1);
    27.      error_reporting($config->error_reporting);
    28.      ini_set(‘display_errors’, 1);
    29. define(‘JDEBUG’, $config->debug);
    30. * Joomla! framework loading.
    31.    jimport(‘joomla.error.profiler’);
    32.    $_PROFILER = JProfiler::getInstance(‘Application’);
    33. // Joomla! library imports.
    34. jimport(‘joomla.application.menu’);
    35. jimport(‘joomla.environment.uri’);
    36. jimport(‘joomla.html.parameter’);
    37. jimport(‘joomla.utilities.utility’);
    38. jimport(‘joomla.event.dispatcher’);
    39. jimport(‘joomla.utilities.arrayhelper’);

    Форматируй код в редакторе. М.

    Последнее редактирование модератором: 13.01.2016

  4. |title|

    Offline

    |title|

    Активист

    Регистрация:
    19.09.2014
    Сообщения:
    105
    Симпатии:
    26
    Пол:
    Мужской

    Попробуй добавить в 31 строку —

    1. require_once JPATH_LIBRARIES.‘/import.legacy.php’;

    или обнови еще раз джумлу))

  5. Offline

    SLWm

    Недавно здесь

    Регистрация:
    13.01.2016
    Сообщения:
    7
    Симпатии:
    0
    Пол:
    Мужской

    огромное спасибо) ошибка исчезла! теперь пишет вот это:

    Warning: session_start() [function.session-start]: Cannot send session cookie — headers already sent by (output started at /home/host1264615/kprfkh.ru/htdocs/www/libraries/legacy/error/error.php:1) in /home/host1264615/kprfkh.ru/htdocs/www/libraries/joomla/session/session.php on line 658

    Warning: session_start() [function.session-start]: Cannot send session cache limiter — headers already sent (output started at /home/host1264615/kprfkh.ru/htdocs/www/libraries/legacy/error/error.php:1) in /home/host1264615/kprfkh.ru/htdocs/www/libraries/joomla/session/session.php on line 658
    Error displaying the error page: Application Instantiation Error: Could not connect to MySQL.

    чего с этим делать?)

  6. |title|

    Offline

    |title|

    Активист

    Регистрация:
    19.09.2014
    Сообщения:
    105
    Симпатии:
    26
    Пол:
    Мужской

    Ошибка то исчезла, а в админку пускает? Лучше обновиться уже до последние версии

  7. Offline

    SLWm

    Недавно здесь

    Регистрация:
    13.01.2016
    Сообщения:
    7
    Симпатии:
    0
    Пол:
    Мужской

    не до админки пока не пускает, просто прежнюю ошибку убрали, что хорошо, но получили две новые, что не очень)

    то есть я обновляю до 3.4.8?
    а хуже точно не будет?,)

  8. |title|

    Offline

    |title|

    Активист

    Регистрация:
    19.09.2014
    Сообщения:
    105
    Симпатии:
    26
    Пол:
    Мужской

    а это я не знаю) лучше бекап сделать, а еще и админка не доступка, а как обновить не через админку…я не в курсе, бекап сделать на хосте. Иль ожидай умов великих

  9. Offline

    SLWm

    Недавно здесь

    Регистрация:
    13.01.2016
    Сообщения:
    7
    Симпатии:
    0
    Пол:
    Мужской

    бекап сделать не проблема — проблема именно с попаданием в админку)
    Ладно огромное спасибо за помощь, подожду мож кто еще что умное посоветует…

  10. woojin

    Offline

    woojin

    Местный
    Команда форума
    => Cпециалист <=

    Регистрация:
    31.05.2009
    Сообщения:
    3 206
    Симпатии:
    334
    Пол:
    Мужской

    сейчас по какой причине не пускает?
    какие ошибки?

  11. Offline

    SLWm

    Недавно здесь

    Регистрация:
    13.01.2016
    Сообщения:
    7
    Симпатии:
    0
    Пол:
    Мужской

    Warning: session_start() [function.session-start]: Cannot send session cookie — headers already sent by (output started at /home/host1264615/kprfkh.ru/htdocs/www/libraries/legacy/error/error.php:1) in /home/host1264615/kprfkh.ru/htdocs/www/libraries/joomla/session/session.php on line 658

    Warning: session_start() [function.session-start]: Cannot send session cache limiter — headers already sent (output started at /home/host1264615/kprfkh.ru/htdocs/www/libraries/legacy/error/error.php:1) in /home/host1264615/kprfkh.ru/htdocs/www/libraries/joomla/session/session.php on line 658
    Error displaying the error page: Application Instantiation Error: Could not connect to MySQL.

    вот они ошибки, сможешь подсказать как ЭТО исправить?

  12. woojin

    Offline

    woojin

    Местный
    Команда форума
    => Cпециалист <=

    Регистрация:
    31.05.2009
    Сообщения:
    3 206
    Симпатии:
    334
    Пол:
    Мужской

    для начала посмотри что с соединением с БД
    в последней ошибке сказано что невозможно соединиться с БД
    и почисти таблицу сессий

  13. OlegK

    Offline

    OlegK

    Russian Joomla! Team
    Команда форума
    ⇒ Профи ⇐

    Регистрация:
    17.01.2011
    Сообщения:
    7 813
    Симпатии:
    768
    Пол:
    Мужской

    А открыть файл и посмотреть, сравнить с файлом из чистого архива. И проверь сайт в поисковике, сколько хакеры успели спама залить в гугл,яндекс

  14. Offline

    SLWm

    Недавно здесь

    Регистрация:
    13.01.2016
    Сообщения:
    7
    Симпатии:
    0
    Пол:
    Мужской

    а вот этот момент можно поподробнее?
    как именно это можно проверить?

  15. OlegK

    Offline

    OlegK

    Russian Joomla! Team
    Команда форума
    ⇒ Профи ⇐

    Регистрация:
    17.01.2011
    Сообщения:
    7 813
    Симпатии:
    768
    Пол:
    Мужской

Поделиться этой страницей


Форумы Joomla! CMS

Error

In Joomla 4 this PHP error appears:

Class 'JDispatcher' not found
Probable cause

If you are Smart Slider user for many years now and you used Smart Slider 2 too, it is possible that on your website you still have its files, which can create this error message. This is the list of folders created by Smart Slider 2, which should be deleted:

administratorcomponentscom_smartslider2
componentscom_smartslider2
librariesnextend
modulesmod_smartslider2
pluginsnextendslider[*]
pluginssystemnextendlibrary

Default cache folder:
medianextend

Did this answer your question?


Thanks for the feedback

There was a problem submitting your feedback. Please try again later.

Last updated on January 5, 2023

Понравилась статья? Поделить с друзьями:
  • Clash of clans как изменить вид деревни
  • Clarke error grid
  • Clang fatal error iostream file not found
  • Clang error unsupported option fopenmp
  • Clang error no such file or directory