Closed (fixed)
Project:
Google reviews
Version:
1.1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
22 Mar 2026 at 16:55 UTC
Updated:
17 Oct 2026 at 22:45 UTC
Jump to comment: Most recent
Comments
Comment #3
mrshowermanComment #6
mxh commentedComment #9
mxh commented@sleitner Thanks a lot for updating MR10 and for taking the time to work on this feature request.
I had a brief look at the committed changes. Some of the additional changes seem to go a bit beyond the scope of the original request and may have some UX implications. For example, displaying the Place ID as a disabled text field in the form could be somewhat confusing for editors, since it is not necessarily clear what the value represents or why it cannot be edited. This is of course a matter of UX preference, but for this issue I would prefer to stay closer to the original scope.
Since we are still using the legacy API, it also looks like the recent refactorings caused the
place_idarray entry to no longer be present. This results in a PHP warning when rendering an item using thegooglereviews_rating_blocktheme function.I therefore added the
place_idvalue back in the same way it was handled up to version 1.1.3:https://git.drupalcode.org/project/googlereviews/-/merge_requests/15/dif...
As the previous patch no longer applied cleanly to 1.1.4, and since I wanted to keep the implementation focused on the functionality requested in this issue, I rerolled the current patch, restored the missing
place_identry, and kept the changes aligned with the original feature request.For that reason, I created MR15 as an updated version and marked MR10 as hidden.
Again, thank you very much for your contribution and for spending time on this.
Comment #10
sleitner commented@mxh , @mrshowerman thank you very much for your contribution to the googlereviews module.
The place ID is the value which is saved for the field not the search text, so it made it easier to debug problems. Now I added the place ID to the search result as well.
The
place_idarray entry was not missing, because it is now part of the request scope and therefore part of the result array.Without v1 support for fields, it can't be merged, because the API version is a global setting.
Comment #12
sleitner commentedMR10 released as 1.1.5-alpha1