dapsuk 0 Report post Posted May 29, 2010 Hi, Im seriously considering purchasing iBlogPro4, but have just seen that WP3 is nearing completion. Will iBP4 be updated to work with WP3, or will it then evolve to iBP5 and I'll have to buy that to work with WP3? Hope I've posted this in the right place and sorry if you have already answered this previously. Thanks Stu Share this post Link to post Share on other sites
Andrew 207 Report post Posted May 30, 2010 Already tested the themes with wp3.0; they work great. You will get all the features, as advertised, and with no errors. We have also done some development for the new menu feature, and other new 3.0 features. Full support for these will be offered in updates once it's out. So yeah the themes work great with WordPress 3.0 Share this post Link to post Share on other sites
dapsuk 0 Report post Posted May 30, 2010 Thats great news, and thanks for getting back so quickly. You guys could teach some very big companies a lesson in customer service (oh and Kudos on the design work - 10/10) Share this post Link to post Share on other sites
bryan-hadaway 3 Report post Posted June 1, 2010 Good to hear you got your answers. Thanks, Bryan Share this post Link to post Share on other sites
salesorigintechnet 0 Report post Posted June 18, 2010 I have iblogpro4 and did the upgrade to WordPress 3 and everything works except the menu items (pages) at the top.. They are all gone? Any ideas? Share this post Link to post Share on other sites
Andrew 207 Report post Posted June 18, 2010 Yes, just add the pages back via the new WP menus feature... Share this post Link to post Share on other sites
mranespacbellnet 0 Report post Posted June 18, 2010 I had the same problem. I reverted back to iBlogPro v4.1.0 and the menus returned. Seems that something in one of the updates between v4.1.0 and v4.1.2, in conjunction with the WP 3.0 upgrade, broke the menus. Will this be addressed in an upcoming update? I'm hesitant to add them back via the new WP 3.0 menus feature for fear of the next update from PageLines breaking them again. Seems like the fix ought to come from PageLines. Mark Share this post Link to post Share on other sites