This topic was marked solved by live627, on February 23rd, 2013, 12:41 AM
« Bug in menu on hovering username.
Uninitialized string offset in Subs-BBC.php, line 1133
Quick edit bug: Quotes turn into backslash »
Uninitialized string offset in Subs-BBC.php, line 1133
« on February 21st, 2013, 05:51 PM »Last edited on February 21st, 2013, 05:55 PM by Nao
I was browsing a topic on this site and got these errors:

Code: [Select]
Notice: Uninitialized string offset: 0 in /wedge/Sources/Subs-BBC.php on line 1133

Notice: Uninitialized string offset: 0 in /wedge/Sources/Subs-BBC.php on line 1133

Notice: Uninitialized string offset: 0 in /wedge/Sources/Subs-BBC.php on line 1133

...

Screenshot attached. After reloading the page the errors disappear.

EDIT: The same just happened when opening my PMs here.

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Uninitialized string offset in Subs-BBC.php, line 1133
« Reply #1, on February 21st, 2013, 05:58 PM »
It's not that 'the errors disappear', it's that they disappeared, period...

I was simply emptying the cache. Which needed emptying after I'd just updated the website to rev 1942 (so, it has 10 days worth of new features, including the new language caching feature, which will hopefully help Pete test it on a wider scale.)

You just happened to refresh the page in the 2 minutes between finishing the upload and me finishing emptying all caches. ;)

:edit: Please report if you find the error shows up again, though.
Posted: February 21st, 2013, 05:55 PM

PS: so, it takes a bug report to get you to post eh? :lol:
Posted: February 21st, 2013, 05:57 PM

Okay, found a bug that I couldn't have seen in my test site because of me having just a single account to test with...
(It's with the user mini-menu.)
Re: Uninitialized string offset in Subs-BBC.php, line 1133
« Reply #3, on February 22nd, 2013, 05:11 PM »
Quote from Nao on February 21st, 2013, 05:58 PM
It's not that 'the errors disappear', it's that they disappeared, period...

I was simply emptying the cache. Which needed emptying after I'd just updated the website to rev 1942 (so, it has 10 days worth of new features, including the new language caching feature, which will hopefully help Pete test it on a wider scale.)

You just happened to refresh the page in the 2 minutes between finishing the upload and me finishing emptying all caches. ;)
Heh, glad it's nothing too serious lol.
Quote
:edit: Please report if you find the error shows up again, though.
I will :)
Quote
PS: so, it takes a bug report to get you to post eh? :lol:
Nah, I just randomly visited Wedge again. I should start posting but when on my phone I'm too lazy to log in lol.

Glad it's fixed :)

live627

  • Should five per cent appear too small / Be thankful I don't take it all / 'Cause I'm the taxman, yeah I'm the taxman
  • Posts: 1,670
Re: Uninitialized string offset in Subs-BBC.php, line 1133
« Reply #4, on February 23rd, 2013, 12:44 AM »
Since the issue seems to be resolved, I'll go ahead and archive this topic.
Posted: February 23rd, 2013, 12:39 AM

Pete, please check the error log: "The email template "pm_email" could not be found."
A confident man keeps quiet.whereas a frightened man keeps talking, hiding his fear.

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Uninitialized string offset in Subs-BBC.php, line 1133
« Reply #6, on February 23rd, 2013, 12:51 AM »
Monkey butts. OK, so here's the deal... the file cache wasn't cleared, and due to a bug in the email template editor, I can't clear just that part of the language cache manually - and I'm reluctant to nuke the entire language cache >_<

All I need is a silly addition of $cachedir to the global list in ManageMail.php, ModifyEmailTemplates() and I could fix all this at least as a workaround >_<
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Uninitialized string offset in Subs-BBC.php, line 1133
« Reply #7, on February 24th, 2013, 07:50 AM »
Is there an admin option to delete the language cache..? Just curious. I can imagine I'd be tired of manually emptying the cache folder everytime I'm uploading a new language update...

(Oh, and probably time to use CACHEDIR or something... ;))

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
« Bug in menu on hovering username.
Quick edit bug: Quotes turn into backslash »