Title: filebase 0.2.9.35 problem
Last modified: August 20, 2016
---
# filebase 0.2.9.35 problem
* Resolved [Adrian](https://wordpress.org/support/users/adriandw/)
* (@adriandw)
* [13 years, 2 months ago](https://wordpress.org/support/topic/filebase-02935-problem/)
* filebase 0.2.9.35 messed up the formatting of all pages with wp-filebase shortcodes.
* Maybe 0.2.9.35 introduced a conflict with another plugin, but I wasn’t able to
confirm that or figure out which plugin might have been conflicting.
* I downgraded to filebase 0.2.9.34 and it’s working fine again.
* [http://wordpress.org/extend/plugins/wp-filebase/](http://wordpress.org/extend/plugins/wp-filebase/)
Viewing 13 replies - 1 through 13 (of 13 total)
* [tracy apps](https://wordpress.org/support/users/tray/)
* (@tray)
* [13 years, 2 months ago](https://wordpress.org/support/topic/filebase-02935-problem/#post-3539386)
* interesting. i’m having the same issue. took the same steps and that worked as
well.
* i also noticed (when i was being all stubborn and trying to troubleshoot it a
bit so i didn’t have to downgrade) that the page choked on the first file attachment
in my default format… but not when using the simple format of a link.
* also i noticed this new error across the top of the main WP-Filebase admin screen:
“
File Browser post or page not set! Some features like search will not work. Click
here to set the File Browser Post ID.”
* and the “Post ID of the file browser” setting wouldn’t allow me to leave the
space blank (it would auto populate with a 0 after save), and then gave me an
error message:
“Warning: The Filebrowser page has at least one subpage Contact
us. This will cause unexpected behavior, since all requests to the subpages are
redirected to the File Browser Page. Please choose a Page that does not have
any subpages for File Browser.”
* so.. not sure if that was causing this error or not… or is related at all.
* Plugin Author [Fabian](https://wordpress.org/support/users/fabifott/)
* (@fabifott)
* [13 years, 2 months ago](https://wordpress.org/support/topic/filebase-02935-problem/#post-3539412)
* tray, you can ignore that new error message, it should only show up if you have
actually set the Post ID to something different than 0. Will fix this with the
next update.
* About the formatting issue:
Can you provide a URL of the page? What templates
are affected?
* [tracy apps](https://wordpress.org/support/users/tray/)
* (@tray)
* [13 years, 2 months ago](https://wordpress.org/support/topic/filebase-02935-problem/#post-3539519)
* since the site is live, i just rolled back to the previous version to fix the
formatting. but the even more strange thing about the error was that when i viewed
the source code for the page, the error was not found and all the code was in
tact, all the way to the bottom.
* not sure if that helps at all. if you’d like, i can set up a dev site and try
to replicate the error.
* one other note is that this is on a WordPress multisite setup. not sure if that
makes any difference.
* Thread Starter [Adrian](https://wordpress.org/support/users/adriandw/)
* (@adriandw)
* [13 years, 2 months ago](https://wordpress.org/support/topic/filebase-02935-problem/#post-3539521)
* My site which had this problem is also a live site.
I backed down to 0.2.9.34
so I can’t give you a URL which demonstrates the problem. However mine is not
a multisite setup. I think there must have been some php problem which prevented
the complete page being generated because the widgets which normally appear in
the right navbar didn’t show. Previous errors like this have been caused by a
variable naming conflict.
* Plugin Author [Fabian](https://wordpress.org/support/users/fabifott/)
* (@fabifott)
* [13 years, 2 months ago](https://wordpress.org/support/topic/filebase-02935-problem/#post-3539531)
* Its most likely a syntax error in your file template. Please post the code here.
* Before 0.2.9.35, html comments in templates were removed. This has changed since
it also strips embedded JavaScript code.
* Now with a syntax error in a template, it can happen that there’s a HTML comment
begin ()
* [tracy apps](https://wordpress.org/support/users/tray/)
* (@tray)
* [13 years, 2 months ago](https://wordpress.org/support/topic/filebase-02935-problem/#post-3539611)
* alright. i re-updated my plugin, now that it’s the middle of the night. the template
that seems to be “choking” is the “default” template. (code pasted below) i didn’t
change this template at all, so it should still all be the same as what came
with the plugin originally.
* ```
```
* [tracy apps](https://wordpress.org/support/users/tray/)
* (@tray)
* [13 years, 2 months ago](https://wordpress.org/support/topic/filebase-02935-problem/#post-3539612)
* ok. nevermind. it seems like the problem resolved itself for me after downgrading,
and re-upgrading again… strange.
* Thread Starter [Adrian](https://wordpress.org/support/users/adriandw/)
* (@adriandw)
* [13 years, 1 month ago](https://wordpress.org/support/topic/filebase-02935-problem/#post-3539622)
* I reinstalled 2.9.35
the problem of messed up formatting is still present I
looked in the generated HTML and found an unclosed comment like you suggested:
`
* Thread Starter [Adrian](https://wordpress.org/support/users/adriandw/)
* (@adriandw)
* [13 years, 1 month ago](https://wordpress.org/support/topic/filebase-02935-problem/#post-3539624)
* This unclosed comment looks as though it’s in a section of code generated by
WP-Filebase 2.9.35
Here is a longer extract
* ```