Jump to content

Recommended Posts

Posted

Searching for "aviation" doesn't find the topic titled, "Aviation facts".

Search for "feats" is not finding the below topic but finds the same topic using "reels" in the title -

"Risky feats and stunts for reels  and views!"

Posted

Is this something you're encountering on your own community or are you able to replicate here? As I am not seeing this pattern:

Could contain: Page, Text, File, Webpage, Person

Posted
7 hours ago, Marc said:

Please provide an example topic you expect to be found with those keywords, so I can take a look

1) Aviation facts

2) Risky feats and stunts for reels  and views!

The first one is searchable by "facts" but not by "aviation".

The second one is searchable by "reels" or "stunts" but not by "feats"

Posted

The second one shows "Risky feats and stunts for reels and views!" in search results but its underlying link on the search results is -

https://www.telugus.com/topic/2142-risky-stunts-for-reels-and-views

(missing "feats" in the URL probably the link did not get updated after editing the title and the reason why it is not finding when searched by "feats")

When we click on it in the search results, it goes to -

https://www.telugus.com/topic/2142-risky-feats-and-stunts-for-reels-and-views

Is there a difference between -

  • editing the title by long-clicking on the title (click-and-hold to edit in place) or
  • editing the title by editing the topic?

Do both the above edits follow the same logic and control flow in the backend?

Posted
1 hour ago, WebCMS said:

Is there a difference between -

  • editing the title by long-clicking on the title (click-and-hold to edit in place) or
  • editing the title by editing the topic?

Do both the above edits follow the same logic and control flow in the backend?

There are no differences. In my testing they save the exact same way.

I have noticed some other issues on your community which are related to your language pack so I would advise switching to an unmodified language pack if you're seeing odd HTML items.

Regarding search though, I also found something our developers will need to resolve so I have transferred this to a ticket. Please watch your email for further correspondence.

Posted (edited)
29 minutes ago, Jim M said:

I have noticed some other issues on your community which are related to your language pack so I would advise switching to an unmodified language pack if you're seeing odd HTML items.

We see some odd rendering when we changed the "search" string (Search) to "Site Search" - it is trying to render the input and HTML as well in some areas inside ACP. Nothing like this happened with other lang string modifications.

Edited by WebCMS
Posted
32 minutes ago, WebCMS said:

We see some odd rendering when we changed the "search" string (Search) to "Site Search" - it is trying to render the input and HTML as well in some areas inside ACP. Nothing like this happened with other lang string modifications.

You would need to ensure that you have translated it properly as some include items in it which are necessary. If you also put in HTML or anything other than words, we cannot guarantee it will work or cause other issues.

Posted

It was modified for the menu item as under - to differentiate between Site Search and Google Search:

<i class="fa fa-search"></i> Site Search

Could contain: Text

Could contain: Text, Electronics, Mobile Phone, Phone

Posted
49 minutes ago, Jim M said:

If you also put in HTML or anything other than words, we cannot guarantee it will work or cause other issues.

 

Posted

The search language string is used also in other locations, even inside title attributes or other ones. The FA icon HTML you're adding is breaking those HTML elements most likely.

Rather than editing the language strings, editing the template (or making a modification) to add the icon would be your best solution in this case.

Posted
6 hours ago, Jim M said:

Regarding search though, I also found something our developers will need to resolve so I have transferred this to a ticket. Please watch your email for further correspondence.

Apparently, it's not full-text search to fall back on MySQL's stop-words (we don't have the source code).

For instance, it doesn't find anything when searched for "the" but does find results when searched for "and".

It indicates you are using your own custom stop-words. What words will be skipped and not searched?

Posted
On 10/25/2024 at 12:45 PM, Jim M said:

You would need to ensure that you have translated it properly as some include items in it which are necessary. If you also put in HTML or anything other than words, we cannot guarantee it will work or cause other issues.

Now we have 2 language packs (Customized and IC default). We can live with the minor rendering issues inside ACP due to the single string that has HTML for FA until we modify the right template (the last thing we want to do).

The Customized lang pack is Locked and not sure if it will get updated when we apply the monthly IC updates. We don't need the Language dropdown in the footer as both packs are similar with minor label differences. We don't see any group permissions for lang packs to hide them from members (similar to themes/pages).

Should we delete the IC default lang pack? Will deleting it unlock our Customized lang pack?

Posted
13 hours ago, WebCMS said:

The Customized lang pack is Locked

This is due to you have designated it as your default language pack. Therefore, you cannot disable or delete it.

13 hours ago, WebCMS said:

not sure if it will get updated when we apply the monthly IC updates

Non-translated words will be updated per normal. Locked is not related to this.

13 hours ago, WebCMS said:

Should we delete the IC default lang pack?

If you wish to or you can disable if you encounter issues in the future so you can enable it and test.

Posted
2 hours ago, Jim M said:

This is due to you have designated it as your default language pack. Therefore, you cannot disable or delete it.

Non-translated words will be updated per normal. Locked is not related to this.

If you wish to or you can disable if you encounter issues in the future so you can enable it and test.

Disabled it.

Thanks!

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...