[Allan]

If you think it’s okay to use the index table engine with the database, you can close this ticket.
I have setup cron update every hour.

Thank you for your answers.

[Allan]

I’ve 436 items indexed, some with long content.

[Allan]

Hi,

Sorry, I didn’t have time to send a message back.

As indicated, I activated the indexing cache: Caching Options > Caching activated + Caching method > Database

In the meantime, I realized that I also had to change the option: Search source > Post Type Search > Search engine > Index table engine

And since indeed, it is very fast, but I do not know if it is a good use or an element which makes it possible to identify the source of the problem in the event of use of the regular engine.

[Allan]

Yes, you can close this ticket.

I have another problem, but I will open a new ticket for this other topic.
In any case, thank you for your efficient product support.
Well done.

[Allan]

Hi,

Yes, I understand the technical consequences and the need for backwards compatibility.
It passes RGAA validation!
Thank you very much, for your intervention.

Best wishes

[Allan]

From what I understand, the recommendation will be not to use a link but a button: https://equalizedigital.com/accessibility-checker/improper-use-of-link/

[Allan]

Hi,

Thanks for this release.
it’s ok for W3C validation, but not in RGAA.

I see the href value of the #asp_showmore anchor, but it doesn’t refer to any ID.
Personally the action at the link returns to the native WP search result page /?s=&asp_active=1&p_asid=2&p_asp_data=1&

Another solution is to relaunch the link with a button.

More information : https://equalizedigital.com/accessibility-checker/broken-skip-link/?php_version=7.4.7&platform=wordpress&platform_version=6.1.1&software=free&software_version=1.3.18&days_active=1

[Allan]

Hi,

I can’t give you these accesses, but I’m a web developer.
tell me the code of the modifications that will not affect the functioning of your plugin and I will put them in place while waiting for the publication of your update.

Have a nice day

[Allan]

Hi,

Thank you for your prompt response.

These 2 problems are the only ones that prevent us from being W3C and RGAA valid.
Our client with standardization and web accessibility objectives.
It is not minor for us as for them.
Technically, however, this should be easily corrected by your teams.

For information, the site is officially presented tomorrow 🙂

[Author]

Posts