[Plugin: Blog-in-Blog] upgrade messed up settings

Hi Joy,
These issues are addressed in version 1.0.4 of the plugin.
many thanks.
Tim

Not all of them are fixed.
This time I upgraded Blog-in-Blog to 1.0.4 on my local host, without upgrading WordPress — so it’s at 3.0.5.
The upgrade ignores my previous settings (most specifically the name of the template file).
The result is that where I had specified one category, one post, no pagination on the home page (in a box so it’s not the only thing on the page), I now get 4 posts from a different category, with pagination.
I had [blog_in_blog category_id=39 num=1 pagination=off template=”bib_update.txt” ] but didn’t get that at all. The category it shows is id 5.

At least the

 and  tags are gone.

I forgot the syntax here. That should say
At least the <pre> and <code> tags are gone.

And I noticed that when I copy version 1.0.2 back over the plugin folder, the name of my template file shows correctly on the settings page, so it’s still there in the database. My site looks fine with 1.0.2.
I think there’s an issue with the template file being in the plugin directory. When I upgrade, it gets deleted, so then it can’t find the one in the settings and reverts to the default. But I thought this version was copying it for me. My uploads folder is called photos (due to converting an existing site to WordPress), and I have a copy of the template there as well, but version 1.0.4 still ignores all template settings and gives me the default.

As an aside, I don’t like the new admin page with the tabs. I’d rather just see it all at once and know it’s all saved with one button. With tabs, I’m never sure what gets saved or if I have to save before switching tabs.

Hi,
I have rolled out a version 1.0.5.
You can now (under the misc tab) chose to have all options shown on one page if you prefer.

Thank you for highlighting the issue with the template file not being found. I think I have fixed this in this version, but I would appreciate you putting it to the test.

Thanks Tim,
That works much better. The upgrade shows no difference on my page (that’s good!).
There is one minor thing, which is the existing template, but I don’t think you can do anything about it. I had the name of the template file in the old version of the options. Now the new version has the default template code. I know if the old template was in the plugin directory it gets deleted before the new code gets to run.
Well actually, I had the template in both the plugin directory and the uploads directory. My page looks correct because the shortcode is specifying the template file, which the new version picks up from the uploads directory (which is named photos). But the options page says it will copy it for me and it didn’t. It shows the default template code instead of my template code.

Hi Joy,
Excellent news.
The template copied to the text box on the admin page is the template named as a file on the old bib admin page.

If you go to /wp-admin/options.php on your site and look for bib_post_template as the option name, you will see the name of the file that would have been looked for. This may not be the same as that in your shortcode?

The template setting in the shortcode is used only for that shortcode instance, and not saved to the database.

You’re right, the old template being in the plugin directory was a pain because it would get deleted, hence having the template in the database now.

Tim

Tim,
I had mine set to bib_update.txt and I had that file in both the plugin directory (which got deleted on upgrade) and in the uploads directory (although it is called photos). I had the same file specified on my shortcode.
So it’s as if the shortcode looks in the correct uploads directory and the upgrade code to copy the old template to the database does not.

Ah yes, the upgrade originally did not look in the correct place. but it should do now. The thing that triggers BIB to look for your default file is that the HTML textarea on the template page is blank. Therefore if you delete the contents of the template textarea, you should find, after saving the page that the textarea has been now correctly repopulated.

Can you try that please?
Thanks
Tim

Tim,
Blanking out the template area and saving worked to pull in my previous default template file. And I only had a copy in the “uploads” folder at the time I did it.
Good job.