Non-critical PHP errors after posting

[RedShirtGuy]

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 24

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 25

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 26

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 27

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 28

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 29

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 30

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 31

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 32

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 33

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 34

Warning: base64_encode() has been disabled for security reasons in [path]/mobiquo/push_hook.php on line 335
Redirecting...

Experienced this a couple of times tonight after posting a comment and starting a new thread.

It appears on the "submission complete, taking you back to your post" page: (/newthread.php?do=postthread&f=36) (f=This forums section)
The redirection is ok, and the postings are still there. I know warnings in PHP aren't necessarily deal-breakers, but thought I'd pass them along to the poor buggers who have to deal with this stuff :)

[Bob38S]

Just had the same message after posting in the joke thread.

Will add screenshot if requested.

[fubar]

Here's mine

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 24

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 25

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 26

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 27

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 28

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 29

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 30

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 31

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 32

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 33

Warning: base64_decode() has been disabled for security reasons in [path]/mobiquo/include/charset.php on line 34

Warning: base64_encode() has been disabled for security reasons in [path]/mobiquo/push_hook.php on line 335
Redirecting...Thank you for posting! You will now be taken to your post. If you opted to post a poll, you will now be allowed to do so.


Click here if your browser does not automatically redirect you. (http://www.woodworkforums.com/showthread.php?t=192060&p=1841450#post1841450)

[rob streeper]

I've been seeing the same error messages for a couple of days.

[ubeaut]

Have passed this on to Steven. Appears to be a hangover from the fixes to malicious code fix of a couple of days ago.:C

:~

[ubeaut]

Steven has had a look at this and here is his comment:

Those are all tapatalk files. Should be fixed now.

I can confirm that the problem is fixed as I I just replied to the below (or above) post from Tapatalk om my mobile.

All the problems appear to have arisen from the fix to the malicious file thing :~ that was happening and hopefully is now fixed for good.

Cheers - Neil :U