I have the same problem after updated from previous version!
message:Warning: Missing argument 1 for WPBannerizeClass::WPBannerizeClass()
Exactly the same here.
How do I roll back to the previous version?
I now have no banner.
I have a backup version (2.8)
http://banhangusa.com/downloads/wp-bannerize-2.8.rar
Hope that we can rollback and wait for our author
When rollback you will see this warning
This WP Bannerize release has a different Database Table struct. WP Bannerize has found an old Database Table. Do you want convert old struct for this release?
then select “Convert Database table” and you will see your old ADs.
–sorry for my bad english!
Thanks for your quick reply.
I’ve downloaded it.
Will wait a while and see if the maker of WP-Bannerize will come with a quick fix.
Haven’t tried it yet.
I’ll wait the day, and see if there’s a quick fix.
Hope the plugin author reads this. There must be more of us out there having the same problems.
Hi,
please download 3.0.1 revision with the fixes.
WordPress seems don’t re-active the plugin after update from backend. I’m still investigate this behaviour.
However, after update from backend, you DEACTIVE/REACTIVE the Plugin and all work properly.
Thanks for notice
Let me know if all works properly
Regards
GF
i’ve install version 3.0.1. Everything is okay. Thank you so much.
All works fine at this end aswell.
thx for the quick update!
friends
I’m having problems with the plugin in the new version of WordPress (3.3.1)
Table wp_bannerize not being created during installation of the plugin.
Does anyone have the structure of the table so that I create?
Hi,
This is a vexing problem, I’m working to fix it!
However, deactive and reactive plugin, the database table should be appear.
Let me know for any news.
regards
GF
Hi,
The table creation error seems to be a problem with sql-query in wpBannerizeTable.sql, in line
free_html text NOT NULL DEFAULT ”,
since BLOB and TEXT columns cannot have DEFAULT values.
That line can’t be changed to be without default value, because the plugins code doesn’t work without it.
Chancing data type to varchar(255) does the trick.
In mysql 5.0.3 or later, maximum length can be 65535.
br,
Esu
Yeah, I fix it as soon as possible.
Thanks for report