COMMUNITY FORUM

Keyword
  1. Forum
  3. Search

Advanced Search

Search Results (Searched for: Fatal Error K2)

  • Bono
  • Bono's Avatar
16 Oct 2023 01:07
Joomla 3 backend doesn't work with PHP 8 was created by Bono

Joomla 3 backend doesn't work with PHP 8

Category: English K2 Community

Hello, I have latest version of K2 2.11.20230505 and latest Joomla 3 3.10.12. I have tried PHP 8 and 8.1 and frontend works fine but backend is broken. I get only white page and in logs I see this: [15-Oct-2023 21:24:25 UTC] PHP Fatal error:  Array and string offset access syntax with curly braces is no longer supported in /home/site/public_html/plugins/system/k2json/
How can I fix this so I can login to backend and so I can use PHP 8/8.1 because frontend works fine.
Thank you
  • Florin Mircea Rusu
  • Florin Mircea Rusu's Avatar
05 Jul 2023 12:22 - 05 Jul 2023 12:26
PHP 8 error at saving a k2 item on Joomla 3.10.11 was created by Florin Mircea Rusu

PHP 8 error at saving a k2 item on Joomla 3.10.11

Category: English K2 Community

Fatal error: Array and string offset access syntax with curly braces is no longer supported in media/k2/assets/vendors/verot/
need to be addressed in all new releases. Replace the string curly braces with square braces on that line.
Otherwise you get a blank page (fatal error) when you add or edit an K2 item ans press "Save" or "Save and close" and the item is not saved in database.
  • Franz Heine
  • Franz Heine's Avatar
20 Jan 2023 12:52 - 21 Jan 2023 00:18
Replied by Franz Heine on topic fatal error after php 8.0 Update

fatal error after php 8.0 Update

Category: English K2 Community

ive updated to k2 V2.11.

And the "strtoupper" error just appears, when i save a k2 item. IT saves the information, but i receive this info.

Do you have maybe a ideal? Because it seems, that just ive this problem.

UPDATE: Foud the error, caused by this plugin:
extensions.joomla.org/extension/additional-categories-for-k2/

Ill contact the programer
  • JoomlaWorks
  • JoomlaWorks's Avatar
27 Dec 2022 19:14
Replied by JoomlaWorks on topic fatal error after php 8.0 Update

fatal error after php 8.0 Update

Category: English K2 Community

The "strtoupper" error is not coming from K2 but something else.

The warning on K2's router is now fixed - simply install getk2.org/downloads/?f=K2_Development_Release.zip on top.
  • Franz Heine
  • Franz Heine's Avatar
21 Dec 2022 01:07
Replied by Franz Heine on topic fatal error after php 8.0 Update

fatal error after php 8.0 Update

Category: English K2 Community

Thx Fotis,

worked! But ive receive following error in the backend:

strtoupper(): Argument #1 ($string) must be of type string, array given
/www/htdocs/w01a9b4f/projekt-lastschrift/libraries/legacy/request/request.php:99

and following on the frontend (debug is active:

Warning: Attempt to read property "alias" on null in /www/htdocs/w01a9b4f/projekt-lastschrift/components/com_k2/router.php on line 283
  • JoomlaWorks
  • JoomlaWorks's Avatar
19 Dec 2022 02:58
Replied by JoomlaWorks on topic fatal error after php 8.0 Update

fatal error after php 8.0 Update

Category: English K2 Community

@Franz Heine
a) This is actually a third-party library issue, not K2. And it's fixed in K2 v2.11 (dev) here: getk2.org/downloads/?f=K2_Development_Release.zip

b) Sticking to PHP 7.4 does not mean your site is at grave danger to get hacked any day now... Most security issues usually relate to performance/reliability, especially on 7.2+ releases.
  • Franz Heine
  • Franz Heine's Avatar
17 Dec 2022 15:30
Replied by Franz Heine on topic fatal error after php 8.0 Update

fatal error after php 8.0 Update

Category: English K2 Community

But it doesnt make sense. The Support for php7 ended. Thats a real security issue. Is there a plan, when k2 will be ready for php8?
  • Franz Heine
  • Franz Heine's Avatar
17 Dec 2022 08:56
fatal error after php 8.0 Update was created by Franz Heine

fatal error after php 8.0 Update

Category: English K2 Community

i receive this error affter updateing my site to php 8.0
Fatal error: Array and string offset access syntax with curly braces is no longer supported in /www/htdocs/w01a9b4f/projekt-lastschrift/media/k2/assets/vendors/verot/class.upload.php/src/class.upload.php on line 2726
  • ricardo calixto
  • ricardo calixto's Avatar
29 Nov 2022 20:03
Fatal error: Array and string offset access syntax with curly braces is no longe was created by ricardo calixto

Fatal error: Array and string offset access syntax with curly braces is no longe

Category: Comunidade K2 Brasil

pagina branca quando tento salvar qualquer artigo no joomla, minha versao do php é a 8, ativei o log e acusa esse erro abaixo:

media/k2/assets/vendors/verot/
plugins/system/k2/
  • JoomlaWorks
  • JoomlaWorks's Avatar
30 Mar 2022 00:57
Replied by JoomlaWorks on topic K2 Error Trying to get property of non-object

K2 Error Trying to get property of non-object

Category: English K2 Community

Michael, a notice doesn't cause a fatal error...
  • Michael Rosa
  • Michael Rosa's Avatar
01 Feb 2022 14:06
Replied by Michael Rosa on topic K2 Error Trying to get property of non-object

K2 Error Trying to get property of non-object

Category: English K2 Community

"Just a notice", it's bad coding and causes fatal error on the site.
  • Anibal Sanchez
  • Anibal Sanchez's Avatar
20 Dec 2021 13:02
PHP 8, New Group => array_merge(): Argument #1 must be of type array, null given was created by Anibal Sanchez

PHP 8, New Group => array_merge(): Argument #1 must be of type array, null given

Category: English K2 Community

Hi,

If you try to create a new group on PHP 8, array_merge(): Argument #1 must be of type array, null given

To fix it:

administrator/components/com_k2/views/usergroup/view.html.php, line 51:

$categories_option = $categories;

if ($categories_option) {
    $categories_options = array_merge($categories_option, $categories);
}

Error impression with  @ doesn't work as before on PHP 8. PHP 8.0: 
@
 Error Suppression operator does not silent fatal errorshttps://php.watch/versions/8.0/fatal-error-suppression


Best Regards
  • Anibal Sanchez
  • Anibal Sanchez's Avatar
22 Nov 2021 19:10
Replied by Anibal Sanchez on topic Fatal error: Array and string offset access syntax with curly braces is no longe

Fatal error: Array and string offset access syntax with curly braces is no longe

Category: English K2 Community

It looks like K2 2.10.3 is not updated to the latest version of the library: github.com/verot/class.upload.php

Best regards
  • Vladislav Zolotaryov (GoldenScrew)
  • Vladislav Zolotaryov (GoldenScrew)'s Avatar
27 Oct 2021 11:01
Fatal error: Array and string offset access syntax with curly braces is no longe was created by Vladislav Zolotaryov (GoldenScrew)

Fatal error: Array and string offset access syntax with curly braces is no longe

Category: English K2 Community

Hello! When I try to save my item, I have the error:

Fatal error: Array and string offset access syntax with curly braces is no longer supported in media/k2/assets/vendors/verot/class.upload.php/src/class.upload.php on line 2726


Do you have update for work on php 8?
  • Oliver Johnson
  • Oliver Johnson's Avatar
09 Sep 2021 22:49 - 10 Sep 2021 00:11
White Screen on Save K2 Item was created by Oliver Johnson

White Screen on Save K2 Item

Category: English K2 Community

Just installed K2 V2.10.3 on a brand new fresh install of Joomla 3.10.1. I've been able to create categories without issue but whenever I try to create an item and save it, I just get a white screen.

Setting Error Reporting to Maximum then gives this error:

Fatal error: Array and string offset access syntax with curly braces is no longer supported in /home/customer/www/*********.co.uk/public_html/media/k2/assets/vendors/verot/class.upload.php/src/class.upload.php on line 2726

This seems to refer to a getsize function but I don't understand enough to know what it's getting the size of or why curly braces are no longer supported.

I'm running PHP 8.0.10 if that makes a difference.

Any ideas?
  • Goble002
  • Goble002's Avatar
07 Apr 2021 13:31 - 07 Apr 2021 13:33
Replied by Goble002 on topic Plugin conflict and recommended PHP settings for upload.

Plugin conflict and recommended PHP settings for upload.

Category: English K2 Community

Hi,

64Mb set for both: No change. Uploads of 5-6Mb file will still cause the error when "Content - jDownloads" plugin enabled. Like explained no issue with 1Mb files.

I have even tried to change the order of the plugin: First, last and middle.
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 8192 bytes) in .../media/k2/assets/vendors/verot/class.upload.php/src/class.upload.php on line 2797


PHP settings:
allow_url_fopen = Off display_errors = On enable_dl = Off file_uploads = On max_execution_time = 30 max_input_time = 240 max_input_vars = 1000 memory_limit = 128M post_max_size = 64M session.gc_maxlifetime = 1440 session.save_path = "/var/cpanel/php/sessions/ea-php74" upload_max_filesize = 64M zlib.output_compression = Off allow_url_include = Off
  • Goble002
  • Goble002's Avatar
05 Apr 2021 18:21
Plugin conflict and recommended PHP settings for upload. was created by Goble002

Plugin conflict and recommended PHP settings for upload.

Category: English K2 Community

Hi,

was getting error below with Front-end editing whenever I edit item. So I switched to latest router as recommended here. www.joomlaworks.net/forum/k2-de/53846-fehlermeldungen-in-router-php-line-292
[b]Notice[/b]: Trying to get property 'alias' of non-object in [b]/home/.../components/com_k2/router.php[/b] on line [b]292[/b]

While uploading 5.8Mb image on Front-end I got following errors.
[b]Deprecated[/b]: Array and string offset access syntax with curly braces is deprecated in [b].../media/k2/assets/vendors/verot/class.upload.php/src/class.upload.php[/b] on line [b]2726[/b] [b]Notice[/b]: Trying to access array offset on value of type int in [b]. ../media/k2/assets/vendors/verot/class.upload.php/src/class.upload.php[/b] on line [b]2726[/b] [b]Notice[/b]: Trying to access array offset on value of type int in ...[b]/media/k2/assets/vendors/verot/class.upload.php/src/class.upload.php[/b] on line [b]2726[/b] [b]Fatal error[/b]: Allowed memory size of 134217728 bytes exhausted (tried to allocate 8192 bytes) in [b].../media/k2/assets/vendors/verot/class.upload.php/src/class.upload.php[/b] on line [b]2797[/b]

So I switch from PHP 7.4 to 7.3. Now only error :
[b]Fatal error[/b]: Allowed memory size of 134217728 bytes exhausted (tried to allocate 8192 bytes) in [b].../media/k2/assets/vendors/verot/class.upload.php/src/class.upload.php[/b] on line [b]2797[/b]

The error was only with big files. No issue with a 350kb jpg. I found out that a plugin was causing the issue : "content jdownloads".

1. Any chance I can uploads working with this plugin ? Change ordering ?

2. A 5.4Mb file will typically take nearly 3 minutes to upload. It might takes longer for slow connections. That said, can you recommend PHP settiongs for my case ?

Actually it is : 
allow_url_fopen = Off display_errors = On enable_dl = Off file_uploads = On max_execution_time = 30 max_input_time = 60 max_input_vars = 1000 memory_limit = 128M post_max_size = 7M session.gc_maxlifetime = 1440 session.save_path = "/var/cpanel/php/sessions/ea-php74" upload_max_filesize = 6M zlib.output_compression = Off
  • saovry
  • saovry's Avatar
11 Mar 2021 05:55 - 11 Mar 2021 07:07
Allowed memory size of 67108864 bytes exhausted (tried to allocate 12288 bytes) was created by saovry

Allowed memory size of 67108864 bytes exhausted (tried to allocate 12288 bytes)

Category: English K2 Community

Hello,
I get this error message
Notice: Trying to access array offset on value of type int in /home/admin/public_html/khmercdp.org/media/k2/assets/vendors/verot/class.upload.php/src/class.upload.php on line 2769 Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 12288 bytes) in /home/admin/public_html/khmercdp.org/media/k2/assets/vendors/verot/class.upload.php/src/class.upload.php on line 2887

Is it error or it is just information becuase I enable Error Reporting: Maximum
Session Settings
Session Handler : PHP
Session Lifetime : 15
Shared Sessions : No
System Cache : NO
  • JoomlaWorks
  • JoomlaWorks's Avatar
06 Mar 2021 13:25
Replied by JoomlaWorks on topic Recoverable fatal error: Object of class stdClass could not be converted to stri

Recoverable fatal error: Object of class stdClass could not be converted to stri

Category: English K2 Community

Try changing "$fields[$k]->field_value[$zone->zone_id]=$obj;" to "$fields[$k]->field_value[$zone->zone_id]=(object) $obj;".

Just a quick thought as I'm not aware of the context in which that codes executes.

In any case, what J2Store did with K2Store and then with the removal of the K2 plugin for J2Store really is a dick move and I would not trust investing on any software from them in the future...
  • JoomlaWorks
  • JoomlaWorks's Avatar
27 Feb 2021 23:38
Replied by JoomlaWorks on topic Recoverable fatal error: Object of class stdClass could not be converted to stri

Recoverable fatal error: Object of class stdClass could not be converted to stri

Category: English K2 Community

This is unfortunately an error with K2Store, not K2. Attach the file here and I'll try and fix it for you.
Displaying 1 - 20 out of 1119 results.
  1. Forum
  3. Search

Powered by Kunena Forum