I'm seeing various "
8: Undefined offset: [12]" errors in
ManageSmileys.php and
Themes.php in a fresh 2.1rc2 install (Debian 8, Postgresql 9.4):
- Type of error: Undefined
- 8: Undefined offset: 1
- hXXps://redacted/~beta-smf/index.php?action=admin;area=smileys;sa=settings;[hexstring]
- /home/beta-smf/public_html/Sources/ManageSmileys.php (Line 129)
- Type of error: Undefined
- 8: Undefined offset: 1
- hXXps://redacted/~beta-smf/index.php?action=admin;area=smileys;sa=modifyset;set=1
- /home/beta-smf/public_html/Sources/ManageSmileys.php (Line 303)
- Type of error: Undefined
- 8: Undefined offset: 1
- hXXps://redacted/~beta-smf/index.php?action=admin;area=smileys;sa=modifyset;set=1
- /home/beta-smf/public_html/Sources/ManageSmileys.php (Line 547)
- Type of error: Undefined
- 8: Undefined offset: 2
- hXXps://redacted/~beta-smf/index.php?action=admin;area=theme;sa=list;th=1
- /home/beta-smf/public_html/Sources/Themes.php (Line 664)
BTW, is there a way to permanently "ignore" specific errors?
No, because they should be solved rather than ignored.
I assumed as much, and from a developer perspective I totally agree.
But from the user (admin) perspective it's kind of tedious to manually delete dozens of duplicate errors that I have already reported upstream. :-X
Yes but if you ignore them, you have to track that and evaluate that which will take more effort and storage than just dealing with it. Also you'd have no way of knowing if it was fixed.
I don't speak PHP (well), so
I can't "deal with it" on a code level anyway. From my perspective, my current error log workflow is as follows:
- delete 95% duplicates that I have already reported, so I can even find the "unhandled" errors
- report new errors upstream and wait to be notified of a fix
I would prefer to be able to skip the first step by ignoring/filtering the duplicates, or at least an option to group/collapse/summarize repeated errors.
(I assume a huge part of my problem is that I'm using a RC version; I haven't used anything else than 2.1rc2 and hope the situation is much better on released versions.)
The problem is that you have to work out what the ones you've seen are, so you have to log them somewhere and every error that comes up, you have to check if you already saw it, which is very quickly a performance drag.
And the minute you install any mod, or perform any change, the entire ignore list is probably invalid anyway.
And yes, the released situation is better though various addons can cause errors too.
Can you run this query in pgadmin
SELECT * FROM smf_settings WHERE variable LIKE 'smiley_sets_%'
The newline character might not be encoded in smiley_sets_names
> select * from betasmf_settings where variable like 'smiley_sets_%';
variable | value
---------------------+-----------------------------
smiley_sets_known | fugue,alienine
smiley_sets_names | Fugue's Set\nAlienine's Set
smiley_sets_default | fugue
(3 rows)
Can't tell if this is how it's supposed to be though.
https://github.com/SimpleMachines/SMF2.1/pull/5596/files
To test this for you you could run this query:
update betasmf_settings set value = 'Fugue''s Set'||E'\n'||'Alienine''s Set' where variable = 'smiley_sets_names'
Thanks, I should have reloaded the thread earlier: I didn't see your last post, but I finally figured it out myself in a similar way:
beta-smf=> update betasmf_settings set value='Fugue''s Set'||chr(10)||'Alienine''s Set' where variable='smiley_sets_names';
UPDATE 1
beta-smf=> select * from betasmf_settings where variable = 'smiley_sets_names';
variable | value
-------------------+----------------
smiley_sets_names | Fugue's Set +
| Alienine's Set
(1 row)
beta-smf=>