• Resolved Cloud Development

    (@clouddevelopment)


    Hello,

    Thank you for writing this plugin.
    Is it possible to ask for a feature?

    In a WordPress Multi-Site environment, network-wide/usable ‘Weather’ objects?
    So each sub-site could use the network-wide ‘Weather’ objects. Including network-wide cache for the data(from the API-calls).

    This could dramatically save in API-calls($$$) when the plugin is used in a network-setup. Administrating the ‘Weather’ objects network wide centrally and applying/using the available ‘Weather’ objects, on/in the sub-sites.

    With kind regards

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Uwe Jacobs

    (@uwejacobs)

    I added this to the list.

    While I am at it, I will also check if I can cache the end result instead of just the API call to OpenWeatherMap. There is considerable logic that converts all the values and then generates the HTML snippets.

    Thread Starter Cloud Development

    (@clouddevelopment)

    Hello Jacobs,

    Thank you for replaying.

    Got no idea how your code or data flow works(knowing its on git-hub).

    Caching eventual weather-object’s there data sounds more logic than caching the API calls. Before different weather-objects use the same API-call… Lots of logic for what a custom-API on a self-hosted web-service could buffer as well. But this is more complex for the web-designer/implementer/use-case.

    Above feature is describing a feature to manage all multi-site-wide weather-objects in the central multi-site-admin, and re-use these weather-objects in the eventual sub-sites there WordPress-admin. All sub-sites could use the multi-site wide available weather-objects(managed from the multi-site-admin) and included/implemented them in the sub-sites.

    On this construction, different sub-sites could use the same weather-object its cached data(and configuration setup). Not creating 4equal weather-objects(manually) on 4 sub-sites to generate 4times the same query(and 4 times the effort to setup the same weather-object).

    Also meaning that the data-source its API setup/credentials are managed just ones in the multi-site-admin, and not for each sub-site individually(as is currently).

    Hope this helps giving context to the request feature.
    Best wishes,

    Plugin Author Uwe Jacobs

    (@uwejacobs)

    After thinking more about the idea to cache the end result, I realized that there is a lot of new logic required to hook into each and everything that invalidates the output cache. For now, I will leave it with just the external API.

    Thanks for the additional info on the multisite install.

    Thread Starter Cloud Development

    (@clouddevelopment)

    Hello @uwejacobs,

    True, I think your current weather-object caching feature is already a useful feature.

    But use-cases of a multisite and how a plugin can be used(and what becomes for a plugin developer available in use-case options): can indeed result in your case to many equal(or matching)-queries, where the weather-object caching ‘currently’ is out of reach(among different subsites).

    But than again, some multisite-setups could like to use different API-credentials for each sub-site. Where a other multisite-setup its use-case could prefer a central-and-single api-setup for your plugin to all sub-sites.

    Query caching and data-mapping could be a brave but large thing to design/build, but the concept of your current weather-object caching is already very efficient.

    Plugin Author Uwe Jacobs

    (@uwejacobs)

    OWM Weather 5.6.0 is now multisite enabled. A short description of the additional settings is under https://ujsoftware.com/owm-weather-blog/multisite-settings/. Let me know in case you run into any issues.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘MultiSite – Network wide/shared Weather’ is closed to new replies.