Bloom for Publishers

Beschreibung

This plugin provides geotagging capabilities for your content and hyperlocal features for your website and newsletters to enable your readers to search and save locations to recieve personalized experiences.
Most features require your website to be a local news outlet that is registered on Bloom.

Screenshots

  • Geotag a location for a post.
  • List of geotagged locations for a post.
  • Local Search plugin to provide hyperlocal reading experience.
  • Readers have the ability to search and save their location preference(s).

Installation

  1. Install Bloom for Publishers plugin
  2. Activate the plugin
  3. Register your website on www.bloom.li
  4. Go to the Bloom Settings page in WordPress to connect your Bloom account
  5. Begin geotagging content
  6. Create plugins on your Bloom account and embed them on your website

FAQ

How do I geotag my Posts?

When creating or editing a Post, scroll down the page to see a section titled „Geotag Locations.“ There’s a button labeled „Add Location“ or „Add Another“ that will display a geotag form when clicked. Search for a location and confirm by selecting a location in the list of results. When you click the Save or Publish button, your Post will be geotagged with the locations you provide.

Why do some location searches not give results?

The location search results will return options that are specific addresses, neighborhoods, postal codes, cities, counties, or other small region. It will not return results for states, countries, or similar larger regional or national geographic area. To help clarify exactly why no results were given, a message should accompany the search result area with more information.

How many locations can I geotag for a Post?

You may have 1 primary location and up to 30 secondary locations geotagged for a Post. Geotagging is optional and is only recommended for locations related to the Post’s content.

How is the location displayed in a Post?

The location you select for a Post is not displayed on the front-end of the webpage unless if you have enabled a Map, Local Search, or other Bloom plugin. By default, the primary location is saved as metadata within the page, which means it will be accessible by other websites and tools, such as search engines and social networks.

Rezensionen

Für dieses Plugin gibt es keine Rezensionen.

Mitwirkende & Entwickler

„Bloom for Publishers“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

Mitwirkende

Übersetze „Bloom for Publishers“ in deine Sprache.

Interessiert an der Entwicklung?

Durchstöbere den Code, sieh dir das SVN Repository an oder abonniere das Entwicklungsprotokoll per RSS.

Änderungsprotokoll

1.7.2

  • Confirmed compatibility with WordPress version 5.9

1.7.1

  • Bug fixed for quotes not being accepted in location fields

1.7.0

  • Better handling for geotagging scheduled posts; Add compatibility for geotagging with Administrative Area Level 1 regions.

1.6.19

  • Bug fix for redundant map images shown in Post page from Reusable Blocks and Widgets.

1.6.18

  • Fixed cache warning from WP VIP compatibility test

1.6.17

  • Improved compability for geotag reminders using legacy editor

1.6.16

  • Added geotag reminders to post edit pages and lists

1.6.15

  • Compatibility added for Google AMP, WordPress 5.8, and minor improvements for better geotagging performance.

1.6.14

  • UX improved for easier confirmation of locations to geotag

1.6.13

  • Improved compatiblity for sending images and excerpts with geotagged posts

1.6.12

  • Improved geocoding compatibility for postal towns

1.6.11

  • Added capability for geotagging by region

1.6.10

  • Compatibility for WordPress 5.7; Better error handling for geotagging;

1.6.9

  • Updated for WordPress 5.6 compatibility; Local Search plugin is now more adaptable for light-color branding palette

1.6.8

  • Improved handling for Google scripts

1.6.7

  • Improved capability for WordPress 5.5 and new variations of Gutenberg blocks

1.6.6

  • Added capability to remove geotags and deactivate post in Bloom from WordPress

1.6.5

  • Improved handling for Google API validation and issues

1.6.4

  • Improved handling of searching for locations to geotag

1.6.3

  • Updated requirements for geotagging routes to include its small region and added better handling for location error messages.

1.6.2

  • New description field added for each geotagged location; Better handling for geotagging place names and geocoding language translation.

1.6.1

  • Added multi-location geotagging capabilities with revised form design

1.5.13

  • Updated compatibility for WordPress version 5.4 and slight design corrections.

1.5.12

  • Improved preview options for search plugin

1.5.11

  • Options added for customizing the Static Map

1.5.10

  • Compatibilty improvements for Nearby Search plugin’s hidden effects

1.5.9

  • Improved handling of geolocation and plugin window effects

1.5.8

  • Cookie data storage is now optional and more compatible for geotagged pages.

1.5.7

  • Adjustments made to location cookie names

1.5.6

  • Added compatibility for search plugin display feature

1.5.5

  • Added settings for Local Search that allow more flexibility for custom UX

1.5.4

  • Added options for accessing user location data and updated styles for WordPress 5.3 compatibility.

1.5.3

  • Adjusted flexibility to geotag intersections

1.5.2

  • Compatibility updated for WordPress v5.3, plugin screenshots updated, search plugin custom links added, and timeout extended for post geotagging.

1.5.1

  • Updates made for Local Search plugin and friendly custom link

1.4.64

  • Adjusted and reduced use of custom fonts within the plugin.

1.4.63

  • Improved compatibility for inline page links to search plugin; Revised FAQ and instructions.

1.4.62

  • Search plugin icon style is now more compatible with any exising website styles

1.4.61

  • Updated URLs for connecting with Bloom’s API and embeddable plugins

1.4.60

  • Minor adjustments to UX for simpler, smoother experience

1.4.55

  • Updated Bloom logo icon

1.4.54

  • Updated Youtube link for tutorial video

1.4.53

  • Adjustment made to plugin admin scripts to reduce unnecessary loading

1.4.52

  • Minor compatibility updates made for new search design

1.4.5

  • Minor compatibility updates to new design version 2 with more control for auto-popup feature

1.4.4

  • Updated search plugin design version to 2.0

1.4.3

  • WordPress 5.2 compatibility updates

1.4.2

  • Added informative geotagging responses; Added instructions for custom search link, and general compatibility updates

1.4.1

  • Improved support for timezones

1.4.0

  • Minor bug fixes and compatibility updates for WordPress VIP

1.3.4

  • Updated configuration settings for Nearby Channel plugin embed

1.3.3

  • Updates for v5.1 compatibility and more intuitive syncing for search plugin settings.

1.3.2

  • Detailed instructions added for new Google API requirements, initial plugin configuration, and Local Search configuration.

1.3.1

  • Minor improvements for stronger compatibility on WordPress 5

1.3.0

  • Enhanced embedded map compatibility with WordPress version 5+

1.2.9

  • Updated plugin compatibility for WordPress version 5.0

1.2.8

  • Minor bug fixes to map button and popup.

1.2.7

  • Added ability to open search with URL parameter

1.2.6

  • Minor maintenance and browser compatibility updates

1.2.5

  • Adjusted search plugin overlay to not cover footer

1.2.4

  • Updated website links for plugins

1.2.3

  • Adjusting how categories are determined for content. No need to pass tags and categories to Bloom anymore.

1.2.2

  • Adjustment made to post type selections