"No posts found", "No pages found" with polylang 0.9

I forgot to mention that for people having no posts being displayed in the admin panel and trying the dev version, they may need to play with the language filter in the admin bar to solve the issue.

Thanks it works for me too now! I just replaced the add filters php with the new version .
Great support!
Whitch file do i have to replace in order to fix the widget bug?
I don t want to load the hole plugin again because everything is working now.
Thanks Susanne

For the widget bug, I modified core.php in 0.9.0.3
For the posts visibility bug, I modified admin-base.php and admin-filters.php in 0.9.0.2

just for information:

the replacement of “add_filter(‘parse_query’,array(&$this,’parse_query’));” also removes the new bug, that the media-layover shows no media-list, if i use an add media option.

0.9 deleted to trash and 0.9.0.3 installed again, and after testing functionalities of the 0.9.0.3 version with my contents in 3 languages (I wold like to show, but is on closed server for the moment) works in same way as older version (0.9)

the only setback for me, was that when trashing 0.9 I lost the connections done on my three languages when 0.9.0.3 is activated. But I only have few testing posts, no problem. perhaps is not need to trash for update in this case, but I’m beginner ??

Thanks chouby for your support!!!

I replaced only the problematic files after the update to 0.9 * because i didn t get a notice in the backoffice to update to 0.9.0.3.and the plugin works great as it worked until now and the language filter is even better, thanks Chouby and thanks for the fast support. I will now update in my other sites too and hope no further problems will accure.
Susanne

Well… just to make a summary and clarify some things. This topic discusses 2 bugs of v0.9 which probably few people will experience.

1st bug reported by jussi.r
In some circumstances, posts, pages and so on are not displayed anymore in the posts, pages lists in the admin panel. As far as I understand, this is due to the new content language filter I added to the admin bar which was not robust enough. During my tests to reproduce the bug, I found that it occurs when editing a language, but when I chose a language in the filter, posts are displayed again.

2nd bug reported by susannetamir
Polylang normally hides languages which have no associated posts or pages in the frontend language switcher (widget or menu). v0.9 does not act like this.

These two bugs should be corrected in the development version. This development version (0.9.0.3 with 4th digit) is not released (i.e. is not proposed in the “automatic” update process). Only the future 0.9.1 will be officially released and proposed for “automatic” update (to come soon).

That means better to wait to update the other sites i have with Polylang!
Thanks again
Susanne

@chouby – Thanks for this great plugin. I’m experiencing error #1.

If i download the dev version with the fix, once the official release is out will I still be able to upgrade “automatically”?

Also, is there any way of me not losing all my existing data when re-installing the plugin? No big deal, just curious…

Merci!

There will be no problem to update automatically. You won’t loose any data if you don’t use the ‘delete’ action in the plugins page. Here, just upload the new files to overwrite the existing ones.

@chouby

I just upgraded to version 0.9.0.5 and the error still isn’t resolved. Have a look at the screenshot below. Note that this is my only active plugin:

Cheers

It’s really strange that the category filter does not display anything (not even “view all categories”).

Which option is selected in the “languages” menu included in the admin bar? What happens if you select another one?

I wonder: Have you a category with empty name which could explain the empty string in the category dropdown filter?

There was no option set! Now that I set an option, “show all languages” it works nicely. I think the issue is that it wasn’t setting a default value for that drop down.

Thanks,

Matt

In fact, the problem is the bug in v0.9. This version is able to save a wrong value. The development version should no be able to save the wrong value, but it does not overwrite the existing value (wrong or right), so you have to use the languages filter at least one time to save a correct value.