You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since this commit: MapServer/MapServer@f478a37
MapServer seems to take a new parameter for config. The MapServer source in Mapcache has not been updated to reflect this change:
My guess is that the new parameter could just take a NULL when called from Mapcache. If I can get a confirmation on this assumption, I'm glad to open a pull request.
The text was updated successfully, but these errors were encountered:
So this is for the experimental MapServer integration. I've never used that feature myself but assuming the mapfile being processed is configured in the mapcache config file and not via a request then you're correct. @tbonfort or @jbo-ads, is that assumption is correct?
@mamaar your plan sounds good to me. If you can test your change locally, confirm it works with null, and then open a pull request with that change, soon-ish, we can include it in the upcoming MapCache release. thanks!
Since this commit: MapServer/MapServer@f478a37
MapServer seems to take a new parameter for config. The MapServer source in Mapcache has not been updated to reflect this change:
mapcache/lib/source_mapserver.c
Line 63 in 2ac1a61
mapcache/lib/source_mapserver.c
Line 232 in 2ac1a61
My guess is that the new parameter could just take a NULL when called from Mapcache. If I can get a confirmation on this assumption, I'm glad to open a pull request.
The text was updated successfully, but these errors were encountered: