Blog Documentation Book a Demo
Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.

[ProxyConnect Addon] Some questions/how to debug?

Das3ZehnDas3Zehn
edited February 2011 in Vanilla 2.0 - 2.8
Sorry for the "not so descriptive title" but I'm kinda stuck currently.
My plans are to use Vanilla ProxyConnect in conjunction with the pligg cms (pligg.com) to provide a forum for a planned project.

During my tests I ran in to the following problems:
1) Pligg generates two extra lines before the actual "UniqueID=" Part starts. I checked the template but as far as I can tell these two extra lines get generated by the core files. Considering that the two lines are generated in two parts of the pligg core files I would prefer to edit the ProxyConnect files - but I got no clue where and how. Any hint?

I'm also desperately looking for a way to debug the whole proxyconnect process - but as far as I can tell there is no way to check logfiles or any other way to check if and where the login progress stops.
Tagged:

Comments

  • Das3ZehnDas3Zehn
    Mmmh.. noone got any idea where to edit the files so it doesn't start at line 0? :(
  • Das3ZehnDas3Zehn
    Well.. Part 1 of my question is fixed: I manually created a file that returns the required info. But it still doesn't work:
    I log out of my site, log back in, switch over to the forums: Nothing
    Trying a different user: log out, log back in, switch to the forums: Nothing.
    No clue at all what's happening and what's not happening - bringing me back to the "how to debug it"-question.

    To be quite honest: As much as I like Vanilla from a technical standpoint I'm currently considering to switch to bloatwareBB aka phpBB as the support here kinda.. well.. is non existant? Tried to find a solution to this problem by doing a forum search: Found a lot of questions and many of them with very detailed info - but most of them don't even get an answer.

    Sorry - but if you want people to use your software maybe also invest some time into either documenting it properly, giving users a chance to debug it OR by support.
  • judgejjudgej ✭
    edited January 2011
    Documentation, documentation and documentation!

    I keep saying this to developers. It does not need to be anything complex - just a text file to describe how a process or protocol works. If that was given then the plugin developers would get help from people who have the ability to read code, but otherwise would not have a clue what the code was trying to do or supposed to do.

    Without that documentation, we are going to see a lot more "doesn't work, can't fix, going elsewhere" type threads.

    The ProxyConnect protocol is a complex part of the forum, and it does have its issues, but no-one but the author has a clue how it works and so we just have to wait. Which is unfortunate.
  • Das3ZehnDas3Zehn
    THAT'S exactly what I'm talking about. I just switched over to phpBB with a lot of addons to "emulate" the Vanilla Forum behaviour. Still don't like this step that much but at least I can help myself and/or get help from other developers. I don't have the time to make a code review just to understand how function xy and addon zx works. I want results in a limited amount of time.
  • matthewkrismatthewkris
    I'm with you guys. I'm frustrated by the lack of support and am verrrrry close to jumping ship.

    That being said, I did manage to get ProxyConnect up and running on my site. Verify that your cookie paths are setup properly and verify that you are actually deleting the Vanilla cookie when you logout.
  • Das3ZehnDas3Zehn
    Seen this, done that - even tried to manually delete it and to use an "Incognito Mode Window" using Chrome (aka "Porn Mode" ;)): No Result.
  • UnderDogUnderDog MVP
    Documentation, documentation and documentation!

    I keep saying this to developers.
    Just turn it around a bit. Try to document after you've asked questions to the developers, then contribute the documentation.

    I'm reading up on the old posts and I'll try to help a bit more, but don't forget that these guys who created vanilla are very very busy.
    Give them a chance.

    There was an error rendering this rich post.

  • judgejjudgej ✭
    edited February 2011
    @UnderDog: I think you misunderstand what I am saying. I am not asking developers to write reams of documentation for every module that they create. I am just suggesting that their *own* notes used to design and develop complex areas of the various protocols are dumped into a readme file. I am a developer, and I do that. The more people that understand the code I write, the more they can help *me* to fix bugs. It works all ways.

    I *hate it* when I see someone frustrated and giving up due to a lack of support. I also realise the developers do not have the time to support the users; that goes without question. It is therefore that much more important to put all those notes out there so that the community can get together to support itself.

    It is just down to what works in a practical real world, with all respect to those who give, and also to those who wish to give, but find the hurdles to jump over too high (like - where to document stuff that we have found...?)
  • UnderDogUnderDog MVP
    edited February 2011
    @UnderDog: I think you misunderstand what I am saying. I am not asking developers to write reams of documentation for every module that they create. I am just suggesting that their *own* notes used to design and develop complex areas of the various protocols are dumped into a readme file.
    I understand your point (this is also the point where I wanted to split off the discussion into a new discussion). Thanks for your input.

    I'm a semi-developer and I don't even make notes.

    I *did* figure out where to document stuff that we have found. It might be something that @Mark and the others don't want us to know, so I won't put it here. Maybe that's something for the next discussion :-)

    This is the starting page for our documentation though:
    http://vanillaforums.org/docs/

    There was an error rendering this rich post.

  • judgejjudgej ✭
    Cool. With Open Source code though, there should not *nothing* that is not fair for documenting. Obviously things can be documented incorrectly, or the code may change, but how it works should still be available to all. Security issues should go through the proper channels to give developers a chance to fix it before security issues become public knowledge.
  • UnderDogUnderDog MVP
    Security issues should go through the proper channels to give developers a chance to fix it before security issues become public knowledge.
    Exactly ;-)
    So... start a discussion and tell what you would like to see documented first :-)

    There was an error rendering this rich post.

Sign In or Register to comment.