Just to give you more info : Chrome was reporting on both ‘No data received’. My apache log was not reporting any errors, however it reported that ‘/wp-admin/admin.php?page=awd_fcbk HTTP/1.1″ 200 0’ needed between 40-120 seconds to return 0 bytes. The amount of time was increasing with time.
It’s due to an RSS error in the plugin. this is fixed now.
Sorry for that.
I have investigated this. Why is the documentation read into through RSS from your website? Why is it not offline / local / or simply linked to outwards?
Currently your plugin jeopardizes the users wordpress installations based on the uptime of your website. That is a huge risk factor and totally unacceptable for any wordpress site operated in any kind of production environment.
This is due to the function that will throw an error if the rss is not ready.
This function should use cache and Asynchronous calls instead of calling the website synchronously.
I am updating the plugin (1.4 release) with a lot of changes that will fixe it.
As for somedays, the website was down due to a disk space, all websites turn down with a timeout error, i am sorry for that.
I am using RSS because i can’t update each time the plugin when i add news, plugins, and others stuff on my website. This take me too much time.
This plugin is free, and if you site is using it in production, you should contact a wordpress devlopper to clean the plugin code depending on your need for the moment.
The 1.4 release represent big changes in the system.
New opengraph interface, new admin interface…
Dear AHWEBDEV,
first of all: thank you for making this plugin free and thank you for your ongoing support.
As to your points :
– the majority of sites who are installing plugins from the wordpress repository are on production environments
– adjusting plugins by wp developers breaks the update cycle and is usually not recommended. Also it defies the purpose of this plugin database if every plugin should be adjusted by wp developers before usage on a live site
– with the massive amount of development websites only surviving for a limited amount before going offline, adding functionality which applies to a certain URL working is deeply discouraged for developers. Imagine you switch jobs in 1 years time and won’t have time and/or money to further support AWD. That would jeopardize your users. Also costs of traffic and backwards compatibility are higher on your side.
– as I see it right now, the RSS functionality of your plugin is not really crucial to its operations, and I would ask you to please disable it per default OR to make it an option with a clear warning of the consequences
As as side-note, or more of a personal request; I am actually a little bit worried over the intrusiveness of your plugin into all areas of wordpress, such as own administration item, own administration tab entry, etc.
I’m sure one of the motivation points for you is to have a prominent plugin, but the FB functionality being just a side-functionality of a WP site I would ask you kindly to take that into regard.
Looking forward to the new version.
Cheers,
D
