[4.0] Additional fields available to display in Search Results + Date ordering fix

[AndySDH]

This serves a similar purpose as this: #24897
But pertains to Search Results Articles instead of Contact Articles.

Summary of Changes

• More Fields are made available to be used and displayed in search results for articles. This adds the ability to use the id, publish_up, introtext and images.

• Also made sure that all of the fields have an AS alias. This wasn't the case before, where some had an alias and some didn't.

• Finally, this makes the search results use the publish_up date instead of the created date when sorting by newest/oldest. The publish_up date makes more sense to use because it's the actual date of the article being published rather than when it was created.

Testing Instructions

None needed. Just little tweaks.

Documentation Changes Required

None.

[richard67]

@AndySDH Drone complains about code style. Here the extract:

FILE: /********/src/plugins/search/content/content.php

FOUND 0 ERROR(S) AND 2 WARNING(S) AFFECTING 2 LINE(S)

285 | WARNING | Line exceeds 150 characters; contains 233 characters
357 | WARNING | Line exceeds 150 characters; contains 233 characters

Can you fix that?

[AndySDH]

@AndySDH Drone complains about code style. Here the extract:
285 | WARNING | Line exceeds 150 characters; contains 233 characters
357 | WARNING | Line exceeds 150 characters; contains 233 characters

Done :)

[richard67]

Drone is ok now. Appveyor failure is not related to this PR.

[ghost]

@AndySDH can you please contact me by franz.wohlkoenig@community.joomla.org?

[Quy]

Please fix conflicting files.

[AndySDH]

I can't. It says "These conflicts are too complex to resolve in the web editor".

So please someone with more knowledge do this please.

[richard67]

@AndySDH You are lucky because the solution is simple: File plugins/search/content/content.php has neem removed in 4.0-dev together with the whole old search plugin, the new default is smart search. So I think if you just remove file plugins/search/content/content.php from your PR, all should be fine. In the GitHub web interface you can do this (as far as I remember) by going to your PR's list of changes, going to that file and then using the "..." link at the right side of the title bar with the path to the file shows a drop-down menu where you (because you are owner) have active menu item "Delete file". Use this and commit directly to your branch patch-4, and all should be fine. Maybe not a bad idea to use the grey button to update your branch to latest base (4.0-dev) changes at the bottom of your PR after having solved the conflict by deleting the file.

[AndySDH]

Well that file was the only one that was modified in this PR :D So I guess if that file is gone, this PR is useless now :D

[richard67]

@AndySDH Oh, silly me, didn't notice that. The old search plugin is still available but on a separate repository. Maybe you should make your PR there? @Hackwar can maybe advise further. This one here can be closed, I think.

[richard67]

@AndySDH I've found it. Please make a PR there for the 4.0-dev branch with the changes of this PR here.
https://github.com/joomla-extensions/search/tree/4.0-dev

[richard67]

@AndySDH ... and this one here you can close.

[AndySDH]

Thanks! This was a very nitpicky PR adding quality of life improvements to the component, but if it's getting decoupled from Joomla / deprecated, then it's probably not worth doing this for it anymore. Maybe could be rather good to check if Smart Search has this instead.

Can you check if Smart Search has these QOL improvements as written above in "Summary of Changes"?

[richard67]

@AndySDH Not sure if I can. I am not using Smart Search normally. Maybe ask @Hackwar ? If he doesn't know, then nobody knows. He knows Smart Search quite well.

[Quy]

Please submit PR to https://github.com/joomla-extensions/search . Thanks.