Php fatal error allowed memory size joomla

Ошибка — Fatal error: Allowed memory size

Ошибка Fatal error: Allowed memory size гласит о том, что вы достигли ограничения по памяти, которые у вас установлены в настройках web-сервера.

Например, текст ошибки:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 71 bytes) in . говорит, что 128 Мб не достаточно (число выше указано в байтах) и его нужно увеличить, либо в указанном месте решить проблему с утечкой памяти.

Решение проблемы с ограничением памяти

Есть два варианта как завершить операцию:

Увеличить лимит по памяти.

Первый вариант сложен и не всегда возможен. Поэтому рассматривать его не будем.

Хотя, зачастую бывает так, что сайт, например, пытается сжать очень большую картинку в другой размер (например, фото в оригинале весит 20 Мб). В этом случае просто используйте оригинальные картинки меньшего размера.

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

Файл php.ini

Это рекомендуемый способ, если вы имеете доступ к файлу php.ini. Данный способ не сработает на многих платных хостингах провайдер, т.к. там закрывают доступ к этому файлу, в целях безопасности. Внимание! Данный способ затронет все ваши сайты и скрипты, находящиеся на сервере.

Откройте файл php.ini и найдите там строку memory_limit:

Через .htaccess в корне сайта

Добавьте в самом начале строку php_value memory_limit 256M. Во время выполнения PHP, запишите перед тяжелыми операциями в php-файл следующую строчку

Как посмотреть, сработало ли?

Откройте в панели управления Joomla информацию о системе

И найдите строку memory_limit

Тоже самое можно сделать через команду .

Если не получилось.

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

Альтернатива

Также оптимизации по памяти можно добиться установкой APC. Он уменьшает потребление памяти в

1,5-2 раза и ускоряет работу всего сайта в целом. Для нормальной работы Joomla + JBZoo обычно хватает 64 Мб (с серьезным запасом на будущее).

Источник

The Joomla! Forum™

Fatal error: Allowed memory size of

Fatal error: Allowed memory size of

Post by fashion24 » Tue Dec 25, 2007 11:04 am

Anyone knows where I can change the allowed size on pictures when adding new products in Virtuemart?
On large pictures I get this error:

Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 5576 bytes) in /home/xtcubeco/public_html/fashion24.no/administrator/components/com_virtuemart/classes/class.img2thumb.php on line 151

Re: Fatal error: Allowed memory size of

Post by pe7er » Tue Dec 25, 2007 4:42 pm

Could you increase PHP’s memory limit from 16 Mb to 32 Mb?

Do you have access to php.ini ?
If so, search for memory_limit and change the value to 32M

If not, do you have a .htaccess file in your Joomla website root folder?
If so, add the following line:
php_value memory_limit 32M

Re: Fatal error: Allowed memory size of

Post by fashion24 » Tue Dec 25, 2007 9:15 pm

Thanks for replying. I have checked the root folder, but theres no .htacces file, only a htaccess.txt file.
No I don’t have access to the php.ini file. Is this something I can ask the hosting company to change?

Or is it possible to add a .htaccess file in the root folder? If yes, what should be in it?

Re: Fatal error: Allowed memory size of

Post by pe7er » Thu Dec 27, 2007 12:49 pm

Re: Fatal error: Allowed memory size of

Post by pitchick » Sun Jan 06, 2008 1:00 am

Re: Fatal error: Allowed memory size of

Post by pe7er » Sun Jan 06, 2008 8:45 pm

Re: Fatal error: Allowed memory size of

Post by naturestemp » Sun Apr 20, 2008 9:53 pm

It seems I don’t have access to php.ini.

I don’t have a .htacess I have a htacess.txt

Does the creation of a ‘blank’ .htaccess interfere with the htacess.txt?

Does blank literally mean that the only thing, literally nothing else, on the page should be: php_value memory_limit 32M

My problem is it is rare that I can install a module without a timeout. I have no problem doing the same thing via WAMP so I’m assuming it’s a memory issue and I’m trying to deal with it without balling up the rest. Hence the overemphasis on detail in this post. Sorry about that.

Читайте также:  Exception доступ к message

Re: Fatal error: Allowed memory size of

Post by trebso » Wed Apr 23, 2008 1:39 pm

pe7er wrote: Could you increase PHP’s memory limit from 16 Mb to 32 Mb?

Do you have access to php.ini ?
If so, search for memory_limit and change the value to 32M

If not, do you have a .htaccess file in your Joomla website root folder?
If so, add the following line:
php_value memory_limit 32M

Having same problem — tried adding that line to .htaccess file, but made no difference. I just pasted it in at the end of the file — is that right?

Re: Fatal error: Allowed memory size of

Post by Alibaba77 » Fri May 16, 2008 9:00 am

pe7er wrote: Could you increase PHP’s memory limit from 16 Mb to 32 Mb?

Do you have access to php.ini ?
If so, search for memory_limit and change the value to 32M

If not, do you have a .htaccess file in your Joomla website root folder?
If so, add the following line:
php_value memory_limit 32M

Having same problem — tried adding that line to .htaccess file, but made no difference. I just pasted it in at the end of the file — is that right?

same to me
I have no access to the php.ini but have a .htaccess.
I added the mention line but nothing changed. Are there additional things to do to make this change working?

Re: Fatal error: Allowed memory size of

Post by bichuoi » Tue Aug 05, 2008 11:53 am

The same problem
when jos_content with 39000 records and Size more than 50Mb it Have an error.

«Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 64 bytes) in /home/thienmin/public_html/timkiemdiachi/libraries/joomla/database/database/mysql.php on line 455»

It run when I delete Some Records (21,501 Table Size 32.8MB)

If I split all content are 2 parts (in other new Category) then It running with no error.
e.g:

But have error when I chose menu list Section

I try fix:
php_value_memory_limit 32M
I also Up to 128MB memory in php.ini but have error on my host.
I try my site with the same Data Base at localhost No error with all records.

This is big problem with me, my site will have 200.000 Items or more in the future.
Help me please!

Please help me. what is solution this this case?
Thanks.

Re: Fatal error: Allowed memory size of

Post by ghog » Wed Aug 13, 2008 2:13 pm

Re: Fatal error: Allowed memory size of

Post by circsoc » Mon Sep 01, 2008 4:04 pm

There is also a third option that doesn’t seem to have been mentioned here. Using the last post as an example, his error is

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 254561 bytes) in /home/wwwmydj/public_html/components/com_sh404sef/shPageRewrite.php on line 244

So ftp to the file shPageRewrite.php in the specified location and edit it as follows.

Near the top there should be a line that looks like this

Simply add the following line below it with the memory limit you want.

This solved a problem I was having uploading large files to RSGallery2, and should work for you too.

Re: Fatal error: Allowed memory size of

Post by ivanichi » Sat Sep 06, 2008 5:44 am

i have install com_jms_0.8.6pre1.zip on my joomla, and i get Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 4864 bytes) in /opt/lampp/htdocs/site/administrator/includes/menubar.html.php on line 602

anybody help me, please..

Re: Fatal error: Allowed memory size of

Post by ivanichi » Sat Sep 06, 2008 6:48 am

this scrren php.ini in : /opt/lampp/etc

max_execution_time = 30 ; Maximum execution time of each script, in seconds
memory_limit = 16M ; Maximum amount of memory a script may consume (16MB)

i have try memory limit with 32M, and then try 128 this message on my screen
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 4864 bytes) in /opt/lampp/htdocs/site/administrator/includes/menubar.html.php on line 648

?? anybody help me??

Re: Fatal error: Allowed memory size of

Post by ivanichi » Sat Sep 06, 2008 7:10 am

Re: Fatal error: Allowed memory size of

Post by phatrick » Wed Oct 01, 2008 9:33 am

Re: Fatal error: Allowed memory size of

Post by fj_marcin » Wed Oct 01, 2008 10:34 am

hi,
it looks like you have the same problem like at http://forum.joomla.org/viewtopic.php?f . &p=1426301
I posted an answer on what you should change.
if you don’t have php.ini then just create it in folder where your file is located which causes the problem.

Best regards,
Marcin K.

Re: Fatal error: Allowed memory size of

Post by tehnz » Wed Oct 22, 2008 7:35 am

@bichuoi posted 29 Dec 2007.

I had the same fatal error message against mysql.php

I am operating from localhost.
I had tried increasing the memory limit to 64M (following the forum above, etc). Successful in increasing the memory as I checked in System Info: PHP Information, but unsuccessful in solving my problem as I still had the fatal error.

However, with the information you supplied in your original query, I decided to try the following to see what would happen if I split my articles into various Categories. At the moment, I had about 7800 published articles in the one Category.
Hence I split them to three Categories, containing about 3600, 3200, and 1000 published articles respectively.
YIPPEE, no more fatal error. My problem solved.

I tried to search in the forum and documentation as to whether there is a memory limit per category but to no avail.

Читайте также:  Error occurred while performing the seed operation

I have posted this cos I think the fatal error message that others get (against different filenames) refers to the limits set for different ‘things’ and not to the overall limited memory in the site/system/server. Any comments?

Re: Fatal error: Allowed memory size of

Post by wegngis » Tue Jan 06, 2009 10:52 pm

I don’t have access to the main server php.ini, I simply put a custom php.ini in the root and /administrator folders.

Cheers, and thanks!

Re: Fatal error: Allowed memory size of

Post by mowahhed » Mon Feb 09, 2009 8:18 pm

Re: Fatal error: Allowed memory size of

Post by Swaino » Fri Jun 12, 2009 1:16 pm

I am in the process of building a site here http://designtech.shivatechnology.net

It was fine yesterday morning, I was able to access the back door of the site and the front end. Towards the end of the day though I could load the back end but the front end wouldn’t appear? Now today I cannot access either, when I tried earlier i got the error Database Error: Unable to connect to the database:Could not connect to MySQL in the browser window

I have spoken with my host company and they corrected the problem so the backend appears (it seemed MySQL had stopped running because of a memory shortage) but were unable to correct the front end and passed along the following error message

Fri Jun 12 11:10:05 2009] [error] [client 84.45.186.74] PHP Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 40961 bytes) in /home/sites/designtech/public_html/libraries/joomla/application/module/helper.php on line 172
*** glibc detected *** /usr/sbin/httpd: double free or corruption (!prev): 0x0b480860 ***
[Fri Jun 12 11:10:40 2009] [error] [client 66.249.71.226] PHP Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 40961 bytes) in /home/sites/designtech/public_html/libraries/joomla/application/module/helper.php on line 172
*** glibc detected *** /usr/sbin/httpd: double free or corruption (!prev): 0x0b484710 ***

I have tried over writing the helper.php file with a fresh one from J!.5.11 zip but with no problems and not being a php programmer am stumped. I have also tried the things listed above, i dont have access to php.ini but i have tried the htaccess idea without luck. The hosts have tried changing the max memory from 16 to 32 but then the error occurs in line 173 as opposed to 172.

Has any body experienced this and corrected it? Im not sure if its the 1.5.11 upgrade but i really cant think of anything else that may have caused this.

Источник

The Joomla! Forum™

Fatal error: Allowed memory size of

Fatal error: Allowed memory size of

Post by theprincy » Mon May 14, 2018 2:33 pm

Before posting I increased the memory, looked for any other 3rd on the web but I did not find anything error goes out, going in system -> global configuration or user -> manage or a random components

Fatal error: Allowed memory size of 10485760000 bytes exhausted (tried to allocate 262144 bytes) in /var/www/virtual/XXXXXXXXXXXXX/htdocs/libraries/src/Helper/UserGroupsHelper.php on line 169

Fatal error: Allowed memory size of 10485760000 bytes exhausted (tried to allocate 262144 bytes) in Unknown on line 0

Fatal error: Allowed memory size of 10485760000 bytes exhausted (tried to allocate 262144 bytes) in Unknown on line 0

I also tried to install it on a server with 32gb of ram but I have the same problem

Re: Fatal error: Allowed memory size of

Post by creativesights » Mon May 14, 2018 9:11 pm

Re: Fatal error: Allowed memory size of

Post by AMurray » Mon May 14, 2018 9:17 pm

Please actually post the results of the FPA into this forum. Follow the instructions and post the output to a reply.

I can’t run the script, my browser security(mcafee web advisor) says it’s a ‘dangerous/malicious/risky site’. I’m sure the FPA script is fine, but your site is the problem.

Re: Fatal error: Allowed memory size of

Post by theprincy » Tue May 15, 2018 6:35 am

Re: Fatal error: Allowed memory size of

Post by theprincy » Tue May 15, 2018 6:40 am

Re: Fatal error: Allowed memory size of

Post by sozzled » Tue May 15, 2018 8:28 am

Re: Fatal error: Allowed memory size of

Post by theprincy » Tue May 15, 2018 8:40 am

Basic Environment :: wrote: Joomla! Instance :: Joomla! 3.8.5-Stable (Amani) 6-February-2018
Joomla! Platform :: Joomla Platform 13.1.0-Stable (Curiosity) 24-Apr-2013
Joomla! Configured :: Yes | Writable ( 644 ) | Owner: —protected— . (uid: 1/gid: 1) | Group: —protected— (gid: 1) | Valid For: 3.8
Configuration Options :: Offline: 0 | SEF: 1 | SEF Suffix: 1 | SEF ReWrite: 1 | .htaccess/web.config: Yes | GZip: 1 | Cache: 1 | CacheTime: 30 | CacheHandler: file | CachePlatformPrefix: 0 | FTP Layer: 0 | Proxy: 0 | LiveSite: https://dimensionedelse.notelseit.com | Session lifetime: 15 | Session handler: database | Shared sessions: N/A | SSL: 0 | FrontEdit: 1 | Error Reporting: default | Site Debug: 0 | Language Debug: 0 | Default Access: 1 | Unicode Slugs: 0 | dbConnection Type: mysqli | Database Credentials Present: Yes

Host Configuration :: OS: Linux | OS Version: 3.2.0-4-amd64 | Technology: x86_64 | Web Server: Apache | Encoding: gzip, deflate, br | Doc Root: —protected— | System TMP Writable: Yes | Free Disk Space : 294.24 GiB |

PHP Configuration :: Version: 7.1.8 | PHP API: fpm-fcgi | Session Path Writable: Yes | Display Errors: 1 | Error Reporting: -1 | Log Errors To: | Last Known Error: | Register Globals: | Magic Quotes: | Safe Mode: | Open Base: /var/www/virtual/notelseit.com/:/opt/phpswitcher/20171020/php7.1/share/pear/ | Uploads: 1 | Max. Upload Size: 150M | Max. POST Size: 400M | Max. Input Time: 4096 | Max. Execution Time: 4096 | Memory Limit: 9096M

MySQL Configuration :: Version: 5.7.20 (Client:mysqlnd 5.0.12-dev — 20150407 — $Id: b396954eeb2d1d9ed7902b8bae237b287f21ad9e $) | Host: —protected— ( —protected— ) | Collation: latin1_swedish_ci ( Character Set: latin1) | Database Size: 58.87 MiB | #of Tables: 165

Detailed Environment :: wrote: PHP Extensions :: Core (7.1.8) | date (7.1.8) | libxml (7.1.8) | openssl (7.1.8) | pcre (7.1.8) | zlib (7.1.8) | bcmath (7.1.8) | bz2 (7.1.8) | calendar (7.1.8) | ctype (7.1.8) | dba (7.1.8) | dom (20031129) | hash (1.0) | fileinfo (1.0.5) | filter (7.1.8) | ftp (7.1.8) | gettext (7.1.8) | SPL (7.1.8) | iconv (7.1.8) | json (1.5.0) | mbstring (7.1.8) | pcntl (7.1.8) | session (7.1.8) | standard (7.1.8) | posix (7.1.8) | Reflection (7.1.8) | Phar (2.0.2) | shmop (7.1.8) | SimpleXML (7.1.8) | soap (7.1.8) | sockets (7.1.8) | exif (1.4 $Id: 8bdc0c8f27c2c9dd1f7551f1f9fe3ab57a06a4b1 $) | sysvmsg (7.1.8) | sysvsem (7.1.8) | sysvshm (7.1.8) | tokenizer (7.1.8) | wddx (7.1.8) | xml (7.1.8) | xmlreader (7.1.8) | xmlwriter (7.1.8) | zip (1.13.5) | cgi-fcgi () | curl (7.1.8) | gd (7.1.8) | imap (7.1.8) | intl (1.1.0) | mcrypt (7.1.8) | mysqlnd (mysqlnd 5.0.12-dev — 20150407 — $Id: b396954eeb2d1d9ed7902b8bae237b287f21ad9e $) | PDO (7.1.8) | mysqli (7.1.8) | pdo_mysql (7.1.8) | Zend OPcache (7.1.8) | Zend Engine (3.1.0) |
Potential Missing Extensions :: mysql | suhosin |
Disabled Functions :: show_source | system | passthru | shell | symlink | proc_open | popen | mail |

Читайте также:  Как установить прошивку magic lantern

Switch User Environment (Experimental) :: PHP CGI: No | Server SU: No | PHP SU: No | Custom SU (LiteSpeed/Cloud/Grid): Yes
Potential Ownership Issues: No

Folder Permissions :: wrote: Core Folders :: images/ (755) | components/ (755) | modules/ (755) | plugins/ (755) | language/ (755) | templates/ (755) | cache/ (755) | logs/ (755) | tmp/ (755) | administrator/components/ (755) | administrator/modules/ (755) | administrator/language/ (755) | administrator/templates/ (755) | administrator/logs/ (755) |

Re: Fatal error: Allowed memory size of

Post by theprincy » Tue May 15, 2018 8:41 am

Basic Environment :: wrote: Joomla! Instance :: Joomla! 3.8.5-Stable (Amani) 6-February-2018
Joomla! Platform :: Joomla Platform 13.1.0-Stable (Curiosity) 24-Apr-2013
Joomla! Configured :: Yes | Writable ( 644 ) | Owner: —protected— . (uid: 1/gid: 1) | Group: —protected— (gid: 1) | Valid For: 3.8
Configuration Options :: Offline: 0 | SEF: 1 | SEF Suffix: 1 | SEF ReWrite: 1 | .htaccess/web.config: Yes | GZip: 1 | Cache: 1 | CacheTime: 30 | CacheHandler: file | CachePlatformPrefix: 0 | FTP Layer: 0 | Proxy: 0 | LiveSite: https://dimensionedelse.notelseit.com | Session lifetime: 15 | Session handler: database | Shared sessions: N/A | SSL: 0 | FrontEdit: 1 | Error Reporting: default | Site Debug: 0 | Language Debug: 0 | Default Access: 1 | Unicode Slugs: 0 | dbConnection Type: mysqli | Database Credentials Present: Yes

Host Configuration :: OS: Linux | OS Version: 3.2.0-4-amd64 | Technology: x86_64 | Web Server: Apache | Encoding: gzip, deflate, br | Doc Root: —protected— | System TMP Writable: Yes | Free Disk Space : 294.24 GiB |

Modules :: SITE :: mod_articles_latest (3.0.0) 1 | mod_tags_popular (3.1.0) 1 | mod_languages (3.5.0) 1 | mod_breadcrumbs (3.0.0) 1 | mod_articles_archive (3.0.0) 1 | mod_articles_news (3.0.0) 1 | mod_feed (3.0.0) 1 | mod_jbcookies (3.0.6) 1 | K2 Users (2.8.0) 1 | MOD_RESLIDER (2.0.8) 1 | AcyMailing Latest Newsletters (1.2.0) 1 | AcyMailing Latest Newsletters (1.2.0) 1 | JEvents — Locations (3.4.17) 1 | mod_banners (3.0.0) 1 | MOD_JEV_SWITCH_VIEW_TITLE (3.4.44) 1 | mod_wrapper (3.0.0) 1 | AcyMailing Module (3.7.0) 1 | mod_custom (3.0.0) 1 | mod_footer (3.0.0) 1 | mod_random_image (3.0.0) 1 | MOD_JEV_LATEST_EVENTS_TITLE (3.4.44) 1 | mod_tags_similar (3.1.0) 1 | mod_finder (3.0.0) 1 | MOD_JEV_CALENDAR_TITLE (3.4.44) 1 | FlexBanners (4.1.08) 1 | Visforms (3.15.0) 1 | mod_users_latest (3.0.0) 1 | mod_stats (3.0.0) 1 | MOD_JEV_CUSTOM_MODULE_TITLE (3.4.44) 1 | MOD_JEV_LEGEND_TITLE (3.4.44) 1 | K2 Tools (2.8.0) 1 | K2 Content (2.8.0) 1 | mod_articles_category (3.0.0) 1 | mod_articles_popular (3.0.0) 1 | SP Page Builder (1.2) 1 | mod_login (3.0.0) 1 | K2 Comments (2.8.0) 1 | EVO frontpage (5.0) 1 | mod_whosonline (3.0.0) 1 | mod_gantry5_particle (5.4.23) 1 | mod_menu (3.0.0) 1 | SCLogin (7.2.3) 1 | K2 User (2.8.0) 1 | mod_related_items (3.0.0) 1 | MOD_RANDOM_IMAGE_EXTENDED (3.2.1) 1 | mod_articles_categories (3.0.0) 1 | MOD_JEV_FILTER_MODULE_TITLE (3.4.44) 1 | mod_syndicate (3.0.0) 1 | mod_search (3.0.0) 1 |
Modules :: ADMIN :: mod_stats_admin (3.0.0) 1 | mod_toolbar (3.0.0) 1 | K2 Quick Icons (admin) (2.8.0) 1 | mod_sppagebuilder_admin_menu (1.3) 1 | mod_sampledata (3.8.0) 0 | mod_feed (3.0.0) 1 | K2 Stats (admin) (2.8.0) 1 | mod_popular (3.0.0) 1 | mod_title (3.0.0) 1 | mod_custom (3.0.0) 1 | mod_latest (3.0.0) 1 | mod_logged (3.0.0) 1 | mod_submenu (3.0.0) 1 | mod_login (3.0.0) 1 | mod_multilangstatus (3.0.0) 1 | AcyMailing DashBoard (1.1.0) 1 | AcyMailing DashBoard (1.1.0) 1 | mod_menu (3.0.0) 1 | mod_sppagebuilder_icons (1.0.2) 1 | mod_version (3.0.0) 1 | mod_quickicon (3.0.0) 1 | mod_status (3.0.0) 1 |

Plugins :: SITE :: Visforms — Visforms (1.0.3) 1 | plg_visforms_spambotcheck (3.4.4) 1 | plg_editors-xtd_module (3.5.0) 1 | plg_editors-xtd_pagebreak (3.0.0) 1 | plg_editors-xtd_readmore (3.0.0) 1 | plg_editors-xtd_article (3.0.0) 1 | plg_editors-xtd_sourcerer (7.1.11) 1 | plg_editors-xtd_fields (3.7.0) 1 | plg_editors-xtd_image (3.0.0) 1 | plg_editors-xtd_menu (3.7.0) 1 | plg_editors-xtd_visformfields (3.4.0) 1 | Search — K2 (2.8.0) 1 | Search — JEvents People/Resour (3.0.38) 1 | plg_search_sppagebuilder (1.4) 1 | plg_search_tags (3.0.0) 1 | plg_search_content (3.0.0) 1 | plg_search_categories (3.0.0) 1 | PLG_JEV_SEARCH_TITLE (3.4.44) 1 | Search — JEvent Locations (3.4.17) 1 | plg_search_newsfeeds (3.0.0) 1 | plg_search_contacts (3.0.0) 1 | JEvents — Enables Facebook Lik (3.0.5) 1 | JEvents — Matching Events Summ (3.3.7) 1 | JEvents — Managed Locations (3.4.17) 1 | JEvents — Managed People (3.0.38) 1 | JEV_CUSTOMFIELDS_PLUGIN_TITLE (3.5.8) 1 | JEvents — Tags for Event Descr (3.1.3) 1 | JEV_STANDARD_IMAGE_AND_FILES_N (3.7.14) 1 | JEV_FEATURED_NAME (3.4.0) 1 | JEV_USERS_TITLE (3.4.2) 1 | plg_quickicon_jce (2.6.26) 1 | plg_quickicon_phpversioncheck (3.7.0) 1 | plg_quickicon_gantry5 (5.4.23) 1 | plg_quickicon_extensionupdate (3.0.0) 1 | plg_quickicon_joomlaupdate (3.0.0) 1 | plg_quickicon_akeebabackup (1.0) 1 | User — K2 (2.8.0) 1 | plg_user_contactcreator (3.0.0) 1 | plg_user_profile (3.0.0) 0 | User — Create JEvents Authoris (3.0.2) 1 | plg_user_joomla (3.0.0) 1 | plg_twofactorauth_yubikey (3.2.0) 0 | plg_twofactorauth_totp (3.2.0) 0 | K2 JEvents Plugin (3.0.6) 1 | PLG_JEV_CORE_CONTENT_PLUGIN_TI (3.4.44) 1 | plg_content_pagebreak (3.0.0) 1 | plg_content_loadmodule (3.0.0) 1 | plg_content_jce (2.6.26) 1 | plg_content_vote (3.0.0) 1 | AllVideos (by JoomlaWorks) (4.8.0) 0 | AllVideos (by JoomlaWorks) (4.8.0) 0 | Content — JEvent Location Embe (3.4.17) 1 | JEvents — Events for people (3.0.38) 0 | plg_content_fields (3.7.0) 1 | plg_content_pagenavigation (3.0.0) 1 | plg_content_joomla (3.0.0) 1 | plg_content_finder (3.0.0) 1 | plg_content_emailcloak (3.0.0) 1 | plg_captcha_recaptcha (3.4.0) 1 | PLG_SYSTEM_BACKUPONUPDATE_TITL (3.7) 1 | AcyMailing : (auto)Subscribe d (5.8.1) 1 | plg_system_highlight (3.0.0) 1 | AcyMailing: override Joomla ma (5.8.1) 1 | plg_system_log (3.0.0) 1 | plg_system_redirect (3.0.0) 0 | plg_system_jce (2.6.26) 1 | plg_system_sourcerer (7.1.11) 1 | System — K2 (2.8.0) 1 | AcyMailing JCE integration (5.8.1) 1 | System — SP PageBuilder (1.3) 1 | plg_system_remember (3.0.0) 1 | System — SP Page Builder Pro U (1.1) 1 | plg_system_ossystem (1.3.0) 1 | PLG_SYSTEM_CMOBILE (2.0.6) 0 | plg_system_updatenotification (3.5.0) 1 | AcyMailing : Handle Click trac (5.8.1) 1 | plg_system_logout (3.0.0) 1 | plg_system_languagefilter (3.0.0) 0 | PLG_SYSTEM_FMALERTCOOKIES (1.3.4) 0 | plg_system_languagecode (3.0.0) 1 | System — jSGCache (1.3.0) 1 | plg_system_gantry5 (5.4.23) 1 | plg_system_fields (3.7.0) 1 | plg_system_sef (3.0.0) 1 | JHackGuard Plugin (2.0.3) 0 | plg_system_regularlabs (17.12.16024) 1 | PLG_SYSTEM_AKEEBAUPDATECHECK_T (1.1) 1 | plg_system_stats (3.5.0) 1 | plg_system_debug (3.0.0) 1 | PLG_SYSTEM_APPSTORE (1.2.0) 1 | plg_system_cache (3.0.0) 0 | PLG_SYSTEM_GWEJSON (3.4.44) 1 | plg_system_p3p (3.0.0) 0 | AcyMailing table of contents g (1.0.0) 1 | AcyMailing : Handle Click trac (5.8.1) 1 | K2 content integration for Acy (2.5.2) 1 | K2 content integration for Acy (2.5.2) 1 | AcyMailing Manage text (1.0.0) 1 | JEvents — AcyMailing Tag (3.1.1) 1 | AcyMailing Tag : Date / Time (5.8.1) 1 | AcyMailing Tag and filter : Co (3.7.2) 1 | AcyMailing Tag and filter : Co (3.7.2) 1 | AcyMailing Tag and filter : in (2.6.0) 1 | AcyMailing Tag and filter : in (2.6.0) 1 | AcyMailing Tag : Manage the Su (5.8.1) 1 | AcyMailing Tag : Subscriber in (5.8.1) 1 | AcyMailing Tag : content inser (3.7.0) 1 | AcyMailing Tag : Website links (3.7.0) 1 | AcyMailing Tag : Joomla User I (5.8.1) 1 | AcyMailing : Statistics Plugin (3.7.0) 1 | AcyMailing Template Class Repl (5.8.1) 1 | AcyMailing : share on social n (1.0.0) 1 | AcyMailing : trigger Joomla Co (3.7.0) 1 | plg_gantry5_preset (5.4.23) 1 | plg_fields_color (3.7.0) 1 | plg_fields_text (3.7.0) 1 | plg_fields_user (3.7.0) 1 | plg_fields_calendar (3.7.0) 1 | plg_fields_sql (3.7.0) 1 | plg_fields_radio (3.7.0) 1 | plg_fields_url (3.7.0) 1 | plg_fields_imagelist (3.7.0) 1 | plg_fields_editor (3.7.0) 1 | plg_fields_usergrouplist (3.7.0) 1 | plg_fields_textarea (3.7.0) 1 | plg_fields_media (3.7.0) 1 | plg_fields_checkboxes (3.7.0) 1 | plg_fields_integer (3.7.0) 1 | plg_fields_list (3.7.0) 1 | plg_authentication_gmail (3.0.0) 0 | plg_authentication_joomla (3.0.0) 1 | plg_authentication_ldap (3.0.0) 0 | plg_authentication_cookie (3.0.0) 1 | plg_installer_jce (2.6.26) 1 | plg_installer_jeventsinstaller (3.4.44) 1 | plg_installer_packageinstaller (3.6.0) 1 | PLG_INSTALLER_FOLDERINSTALLER (3.6.0) 1 | plg_installer_webinstaller (1.1.1) 1 | PLG_INSTALLER_URLINSTALLER (3.6.0) 1 | plg_extension_jce (2.6.26) 1 | plg_extension_joomla (3.0.0) 1 | PLG_FINDER_JEVENTS (3.4.44) 1 | plg_finder_k2 (2.8.0) 0 | plg_finder_sppagebuilder (1.0.0) 0 | plg_finder_tags (3.0.0) 1 | plg_finder_content (3.0.0) 1 | plg_finder_categories (3.0.0) 1 | plg_finder_newsfeeds (3.0.0) 1 | plg_finder_contacts (3.0.0) 1 | plg_editors_jce (2.6.26) 1 | AcyMailing Editor (5.8.1) 1 | plg_editors_tinymce (4.5.8) 1 | plg_editors_codemirror (5.34.0) 1 | PLG_OSMAP_JOOMLA (4.2.12) 1 |

Источник

Smartadm.ru
Adblock
detector