WordPress.org

Forums

[Plugin: Sociable] Save changes gives server error (25 posts)

  1. cyclosity
    Member
    Posted 6 years ago #

    Method Not Implemented

    POST to /wp-admin/options-general.php not supported.
    Apache Server at blog.cyclosity.com Port 80

    When I hit save shanges.

  2. cyclosity
    Member
    Posted 6 years ago #

    Still having the same issue.

  3. cyclosity
    Member
    Posted 6 years ago #

    Still having the same issue. WTF am I supposed to do with this s

  4. cyclosity
    Member
    Posted 6 years ago #

    Method Not Implemented

    POST to /wp-admin/options-general.php not supported.

  5. cyclosity
    Member
    Posted 6 years ago #

    Still can't get around this error...

  6. visual77
    Member
    Posted 6 years ago #

    I ran into this same issue and spent some time debugging it to find the error. I wrote a post on it to help other people get through it.

  7. cyclosity
    Member
    Posted 6 years ago #

    visual :

    Thank you, but unfortunately that's only a work around, and it's getting to the point where I'll have to uninstall sociable because of this stupid bug.

  8. visual77
    Member
    Posted 6 years ago #

    Have you tried just removing Ping.fm from the list of social media sites that Sociable supports? You can do this by editing wp-content/plugins/sociable/sociable.php and remove lines 345 - 349. Those were the lines for me, at least. If you have any experience with PHP syntax, it will be easy to spot, but just remove the item in the array for Ping.fm.

  9. Joost de Valk
    Member
    Posted 6 years ago #

    Sorry that's just a stupid pattern in mod_security, so it's actually their bug, not sociable's.

  10. visual77
    Member
    Posted 6 years ago #

    That's a pretty odd comment. You can do something about it, and get it working for people, but you won't and instead point the blame at someone else.

    Want me to fix it up for you so people can use your stuff on all platforms, since you seem unwilling to do so?

  11. Joost de Valk
    Member
    Posted 6 years ago #

    I'm not willing to remove the option to reorderi sites, and have no time to adjust the way it works, so if you have a patch that makes it work without removing functionality, yes of course you're welcome :)

    BTW: it's not an odd comment, with about 200,000 installs and two people complaining, me thinks the problem isn't too severe.

  12. visual77
    Member
    Posted 6 years ago #

    If it's only two people complaining, then those two people search for that exact error message and find my fix surprisingly often.

    I'll have a diff ready for you before the end of the day tomorrow.

  13. Joost de Valk
    Member
    Posted 6 years ago #

    Well then your fix is more than welcome. I'm sorry if i come across as otherwise, but I get annoyed when people (not you, obviously) complain but don't seem to have any intention of helping out with a fix, either by looking at the code or by asking a developer in a friendly way to have a look at it.

    If someone WTFs me, I'm usually not really too inclined to help anymore, with about 30 plugins and 400,000 users to support, there's better things I can do with my time :)

  14. Joost de Valk
    Member
    Posted 6 years ago #

    BTW: could you test whether it'd be fixed just by renaming ping.fm to pingfm?

  15. visual77
    Member
    Posted 6 years ago #

    I'll give that a shot. I think the regex is just scanning for the word 'ping' and assuming it's an intrusion. My plan is to adjust the array to use numeric keys instead of string keys, and have the site order use those IDs instead of the name of the engine. I can't imagine mod_security freaking out over just numbers and pipes.

  16. Joost de Valk
    Member
    Posted 6 years ago #

    that won't work, as that sitename is used elsewhere...

  17. visual77
    Member
    Posted 6 years ago #

    I finally have some time to debug this issue and now I'm having trouble replicating it. My VM environment just won't throw the error. The environment that I originally had the error is off limits to me at the moment, and I don't know the exact configuration it is working with.

    So... since I'm working blind here, I'll focus on changing that post data to IDs and pipes, correct other calls to make use of this new data structure, and hope it works. I'll post the diff patch once I'm done, but I can't be sure it will actually fix it until I can replicate the bug and try it out in that environment - which would happen Monday when I can access the bugged server again.

  18. visual77
    Member
    Posted 6 years ago #

    I've got a first patch completed and available. Apply this diff to 3.4.3 to take the changes.

    http://www.visual77.com/wp-content/uploads/2009/07/sociable-patch-001

    This *will* fix the errors, but does have some drawbacks. I rearranged the $sociable_known_sites array to use numeric IDs instead of string IDs. I then rearranged the settings form and how it determined active and disabled sites. I've tested with adding, deleting and rearranging sites, along with restoring the settings and viewing it on the posts, it works in all scenarios.

    The drawbacks are mostly dealing with legacy support and continued support. Applying this patch would require redoing the active sites, as the current setting uses strings and this patch does not, but I have a plan to correct that issue. Continued support is fully possible, but future engines have to be added to the end of the array, which would break the alphabetical order. This array would be much better suited to a table in the database, however.

    I found myself having to do some interesting stuff to get it working, especially with that array_merge($active, $disabled) when displaying all the sites. Since array merge scrubs numeric keys, and this patch relies on numeric keys, I had to use a combination of array_combine, array_keys and array_merge to maintain the array as needed and keep functionality intact.

    However, as I said in my last post - I'm working blind, so take this fix with a grain of salt. If I can get my VM to replicate the issue before Monday, I'll do a proper test, otherwise, I will let you know on Monday if this fixes the error in a server that has the error.

  19. visual77
    Member
    Posted 6 years ago #

    Silly me - that whole array_combine trick was unnecessary. I went back and looked at it again, and simply using + to do an array union has the same effect. I just updated the diff to use this more efficient set up.

  20. Joost de Valk
    Member
    Posted 6 years ago #

    pretty ok diff, you missed a couple of things though, which make it impossible for me to use this:

    1. the function sociable_html itself is used by many to include sociable into their themes, and they can use site names now, switching that to numbers is very un user friendly.
    2. said function won't work when people update, as well as their site settings will have to be updated.
    3. there's an API on how to add sites, that has been used by at least 5 other plugins to add sites from their local country

    So, switching to the type of array you're proposing is not an option... We'll have to find another way around this.

  21. visual77
    Member
    Posted 6 years ago #

    Thanks for the feedback. I looked into fixing issues #1 and #2 and decided that I was just adding bandaids that would come back later to suck.

    You were right on saying this change is not ideal. While I could get it to work and play nice with legacy and continued support, it would get awkward.

    I have an idea that adjusts only that hidden input. It would still use numeric IDs instead of string keys, but only that one spot - the array would go unchanged, the database save string would go unchanged, the sociable_html() function would remain, etc.

    I hope to get that diff up tonight, but I can't guarantee it. Tomorrow night, though, if I am unable to finish it tonight.

  22. cyclosity
    Member
    Posted 6 years ago #

    Are the changes that you worked on in the update that was released today? I sure hope so.

  23. tijmz
    Member
    Posted 6 years ago #

    Thanks for the fix - removing Ping.fm from the plugin worked wonderfully.

  24. mattredback
    Member
    Posted 6 years ago #

    thanks visual77 had the same problem and found this post very usefull

  25. ernohannink
    Member
    Posted 5 years ago #

    Although I hate to change a plugin, I just came across the same error and removing Ping.fm worked for me. Thank you visual77

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags