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.

Preview Post 2.2 and Saved Searches and Category Jumper

edited March 2007 in Vanilla 1.0 Help
Hello good folks. I searched and saw some known issues with Preview Post, but not in this particular combination. So hopefully you will be able to help me. The Preview Post 2.2 extension was the last extension I installed. When I activated it, it turns out to not like 2 other extensions, either together or separately, after testing. Issue 01: Preview Post + Saved Searches The Saved Searches feature works, but when using Preview... Fatal error: Call to a member function on a non-object in /home/content/d/i/a/diagonalman/html/forum/extensions/SavedSearches/default.php on line 98 Issue 02: Preview Post + Category Jumper The Category Jumper features works, but when using Preview... Fatal error: Call to a member function on a non-object in /home/content/d/i/a/diagonalman/html/forum/extensions/CategoryJumper/default.php on line 58 Other notes: I am running Vanilla on a shared linux server and permissions seem fine. I've installed more extensions than I currently use, b/c I'm not sure if they're applicable to me any my members yet. I don't know if non-active extensions cause issues. I would expect that they wouldn't, but I'm not a programmer so not sure where to look now. Thanks. INSTALLED EXTENSIONS: BInsertBar 0.1.5 [installed, but not active] Better BB Code 1.0 [installed, but not active] Gig Calendar 1.0 Category Jumper 1.0 DCalendar 1.01 [installed, but not active] Applicant Discovery 1.0 Extended Application Form 1.0 New Applicants 1.2 Page Management Plus 2.4.3 Preview Post 2.2 Saved Searches 2.0 YellowFade Effect 0.1 [installed, but not active] Member List 1.2

Comments

  • It seems strange that all 3 of those extensions are in use here on this forum, arent they?
  • I think we're running PreviewPost 2.1 on here aren't we? I think this is all related to checking if something is there before adding to it...
  • 2.0 actually. That's probably why.
  • Thanks. Is there any way to get a copy of 2.0?
  • 2.1 won't have the problem either and I can send you that. However, the real solution is for the authors of the problematic extensions to update them (of which I am also guilty, but time is short currently).
This discussion has been closed.