Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.

RSS2 in sidebar

edited May 2006 in Vanilla 1.0 Help
How just the Atom comes up and not the RSS2 link on the sidebar on v1? I tried grabbing the files provided by SirNot here http://lussumo.com/community/comments.php?DiscussionID=956&page=2#Comment_13889 but one of the links was dead. ANy ideas?

Comments

  • Yeah I would like to know that too please.
  • MarkMark Vanilla Staff
    If you are using Version 1, the old feed files won't work. I think Sirnot was talking about the old feeds for 0.9.2. If you want the feeds for v1, you'll have to get them from SVN in the extensions folder: http://lussumo.com/svn/vanilla/trunk/extensions/
  • edited May 2006
    Mark- rock on! Thks so much....


    this worked but i still get that pop up "failed to modify extension"
  • MarkMark Vanilla Staff
    Okay, let's get to the bottom of this "failed to modify extension" message.

    1. What OS, Browser, and versions are you using?
    2. Open up js/ajax.js and uncomment line 50 so it looks like this:

    document.location = DataSource;

    This will make it so that the ajax request will instead redirect you to the page that performs the action. So, when you click any ajax button, it will redirect you to the ajax handler page so you can see what exactly is going wrong. If you see any error messages when you try to turn an extension on or off, paste it in here.
  • OS is XP SP2 browser is Firefox 1.5.0.3
    Happend in IE7beta2 also.

    edited the JS and will let u know.
  • Ok I made that change, and when i click on the extension to activate or deactivate all it does it send me to a blank page with the plugin name on it.
  • MarkMark Vanilla Staff
    edited May 2006
    Hmmm. That's what is supposed to happen, so the problem must be occurring somewhere else.

    Okay, change the js file back and let's try something else.

    Open up js/global.js and change lines 162 and 163 to look like this:

    function SwitchExtensionResult(Request) { alert(Request.responseText); var Item = document.getElementById(Request.responseText);

    Then hard-refresh the extension page (so you get the latest js files) and try turning an extension on or off...
  • edited May 2006
    After that change I tried to activate deactivate the extension and I got a pop-up with the name of the Extension > clicked ok > then "Failed to Modify Extension" popup comes up.

    however it is writing to conf/extension.php
  • MarkMark Vanilla Staff
    Okay, the name that comes up: what is it *exactly*?

    I've got to see if I can duplicate this, because it just doesn't make any sense.
  • edited May 2006
    First off I figrued out the problem with the help of jsanders. Apparently the WhosOnline extension was the cause of this problem. I removed the extension from conf/extensions.php and then tried enabling/disabling other plugins and it worked without a hitch.
    see below...
    http://lussumo.com/community/discussion/2144/lace-extension-and-v1/#Item_11

    Once I reactivated the WhoseOnline extension the problems started again. I will provide you the exact details of what happend though when the error did occur.

    Clicked on Extension that I would enable
    Pop came up with the extension name - ie. clicked to enable RSS2 and the pop text would say RSS2 with a small yellow warning sign before it.
    Clicked Ok and the dialogue closed.
    Another dialogue box opens up saying "Failed to Modify Extension"
    Clicked ok
    Activity Indicator continued to spin and just sits there.
    Hard refresh the page and it doesnt look like the extension is enabled, however when looking at conf/extensions.php it did write to the file.
  • yep, can confirm that here too with win + firefox 1.5. With WhosOnline that popup occurs, without it doesn't. The extensions appear to work regardless.
  • MarkMark Vanilla Staff
    Okay, I figured it out.

    The problem was that dknowles had a bunch of white-space at the bottom of his extension after his final ?> declaration. This caused whitespace to also be dumped into the ajax pages and caused the error. I will fix the error, but I guess it should be noted here that you should never have any white-space in your extension files because it could mess up other extensions that try to send headers.
  • MarkMark Vanilla Staff
    Alright, subversion has the fixed code.
  • right on mark... good bit of info about the whitespace.
  • right on mark... good bit of info about the whitespace.
  • Mind me asking how you managed to post that twice? I've been trying to confuse vanilla a number of times and always failed :(
This discussion has been closed.