atoon

BTW:

on all my WP installations:

1) wp-admin and underlying directories are mode 755
and owner is not web server user (e.g apache)
find wp-admin -type d -exec chmod 755 {} \;

2) wp-admin/* files are 644 and owner is not apache
find wp-admin -type f -exec chmod 644 {} \;
find wp-admin -type f -exec chown WEBUSER {} \;

NOTE:
– replace WEBUSER to your web server user name
– assumed is you are in your blog docroot

I installed “Lockdown WordPress Admin” plugin, which hides wp-admin.
still have to check if it helps.

Any comments?

wp-admin/setup-config.php
Note: & 0 39 ; = '

Safety: Thanks for the patch

the other possibility is to change php.ini switch
from short_open_tag = Off
to short_open_tag = On

which I would not recommend.

reason is given as comment in php.ini
—just in case you don’t have it

; This directive determines whether or not PHP will recognize code between
; <? and ?> tags as PHP source which should be processed as such. It’s been
; recommended for several years that you not use the short tag “short cut” and
; instead to use the full <?php and ?> tag combination. With the wide spread use
; of XML and use of these tags by other languages, the server can become easily
; confused and end up parsing the wrong code in the wrong context. But because
; this short cut has been a feature for such a long time, it’s currently still
; supported for backwards compatibility, but we recommend you don’t use them.
; Default Value: On
; Development Value: Off
; Production Value: Off
; https://www.php.net/manual/en/ini.core.php#ini.short-open-tag
—————

check my post for quick fix.

or blog post

Note: This fix is unofficial.

I found the bug.

you have to correct the typo in file
class-sociable_Admin_Options.php
on line 186
change “<?” to “<?php”

for detailed description check my latest blog at blog.admintoon.com