[nicolab292]

Ok, great, thank you.

[nicolab292]

Firefox and Safari on an iPhone 5s seem fine as well. I hadn’t checked on a telephone in the past few days, I was looking on a Macbook.

[nicolab292]

Hello Ernest,

I am using Firefox 78.15.0 under 10.11.6 ; I should have mentioned.

Your fix in the CSS did the trick, now it looks normal.

Thank you,
Nicolas

[nicolab292]

You cannot access this content.

[nicolab292]

Hello Ernest,

Ok ; it is good know that other people have requested that as well, that it is not just our very specific problem.

But I totally understand that it can’t be on top of the list.

Your plug-in is very impressive already in terms of the possibilities that it gives.

All the best,
Nicolas

[nicolab292]

Ah! Thank you for looking. This explains that.

All the documents for the technical section of the website (documentation scans etc.) , and this means a large number of documents, are all in a /docs folder , and were not entered via WordPress.

This is an heritage from the previous non-Wordpress version of the website, and also a way to make the links to these documents “human-readable”.

I thought that the fact of a document being linked to from a WP page would be sufficient for it to be scanned.

I understand now that this is not the way it is setup.

Maybe it would be nice as an extra feature to be able to add a folder to be scanned? Or maybe it doesn’t make sense.

In the meantime I guess we will have to live without the possibility to search on the contents of these documents, as I don’t think we would change all these links.

All the best,
Nicolas

[nicolab292]

You cannot access this content.

[nicolab292]

You cannot access this content.

[nicolab292]

Ok; thank you for trying!

Best regards,
Nicolas

[nicolab292]

Hello Ernest,

Sorry for the delay in answering. I’m not in the lab these days, and I missed the message in the webmail.

Well, from what I can see, now, even with Polylang compatibilty ON, the General search outputs pages in both languages. Try my name ‘Nicolas Rey’ or ‘Kodak’ and you can see this.

So it doesn’t work like I would want it to work: only the current language + custom posts.

Let me know what you think. If it is too complicated, just put it back the way it was, and we’ll just live with what we have I guess…

Thank you , I’ll try to be more careful with e-mails in the coming days.

Best regards,
Nicolas

[nicolab292]

You cannot access this content.

[nicolab292]

You cannot access this content.

[nicolab292]

Hello Ernest,

Yes, it works! Thank you. Now my specific search in my series of custom posts that do not have a language assigned is operational in both the languages that the website has.

I also built a “general search” in all the website, that covers both the main pages (that have two versions for language and are mangaged by Polylang ) AND my custom posts that aren’t managed by Polylang.

But, one of the two things happen:

– if I apply Polylang compatibility, the custom posts are filtered
– if I don’t apply Polylang compatibility, the results in the main pages are doubled : both languages come up

I don’t thing there is way around that, is there? Ideally I would like to have the results in the current language for the main pages + the custom posts. But I understand that this comes from the fact that Polylang filters content that is not in the current laguage, even though these posts are excluded from the scope of what it is supposed to deal with.

Best regards,
Nicolas

[Author]

Posts