zoxee

Divi 3.0 looks a lot like Profit Builder. Nothing new here. PB still the easiest to use for me.

This plugin is awful. While using it, my oven and my fridge stopped working ??
jk… Very good job Emre

• This reply was modified 8 years, 2 months ago by zoxee.

No one ?

any idea ?

You don’t understand, this bug exists since the fresh installs of my blogs,
before anything else comes onto them.
If useful, i can mention that i install all my blogs through Parallels Plesk
and my server runs PHP 5.3.

Thanks Samuel, problem solved!
Now i have another problem, on ALL my blogs, take a look :

https://www.youtube.com/watch?v=TyX6ZQqxiZA

Hopefully you can help me on that one too!

Of course i read the description.

Before 3.5 not only the pingbacks but the whole XML-RPC was considered
a security whole by the WP devs themselves therefore it was COMPLETELY
deactivated by default.

If the pingbacks really were the only problem how come WP devs didn’t
implement your plugin’f functionality inside of wordpress sincethen,
so people are protected but are still able to use the communication functions ?

Simple, because once you open XML-RPC partially, it is already a security risk,
so they decided to leave it fully accessible and functional which isn’t right either,
but i guess it’s to give people like you some work so they have their insignificant
moment of glory. If they only did the job completely which you didn’t..

Your plugin’s name begins with “Disable XML-RPC…” whichs what most non-techie
people who just got aware of the risk will bother to read before they blindly download
your plugin.

This is misleading and you even admit it implicitely by writing :
“This will HOPEFULLY stop some bots from trying to hit your xmlrpc.php file”

The only way to close the security breach is to deactivate the sucker completely.
Period. Have a nice day.