Meta Box

Hey David, thanks for the pointer! I'm using Leaflet on the front-end -- the same library used in MetaBox in my understanding. It doesn't look like the link you posted is using Leafelet, can you point me to the providers that have this option?

Thanks for the info Anh!... That thing about language sucks! I hope it's not a show stopper for my client... or I'll have to revert back to Google Maps 😮

I found that the Location object stores latitude and longitude, so for the time being I'm relying on that to create front-end maps and serving that up through my API.

Weird... I still get nothing to install or update message.

composer clear-cache && composer install
Clearing cache (cache-vcs-dir): /Users/mauro/.composer/cache/vcs
Clearing cache (cache-repo-dir): /Users/mauro/.composer/cache/repo
Clearing cache (cache-files-dir): /Users/mauro/.composer/cache/files
Clearing cache (cache-dir): /Users/mauro/.composer/cache
All caches cleared.
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Nothing to install or update
Generating autoload files

Another note: many plug-ins have the .svn directory inside, is this the intended behaviour? Shouldn't all version control information be removed during the install of the components?

Hi again, please note there is no link to go to Page 2 of this topic on this page.

So, I figured out there are more typos and issues with the provided composer.json file:

• Line 46: "vendor/meta-box/mb-relationsihps/": ["wpackagist-plugin/mb-relationships"],
  Relationships is misspelled, that causes the autoload error below because it places the plug-in in a misspelled directory.

• In the autoload section, the file names are wrong. It appears that the main plug-in file for some of the plug-ins are named mb-[plugin-name].php where the plug-in directory is meta-box-[plugin-name] and MB Text Limiter's main plugin file instead is only named text-limiter.php -- that is confusing. May I suggest in the future to standardise all the naming of both directories and plug-in init files to one naming convention -- be it mb-[plugin name] or meta-box-[plugin name] ?

I guess only admins can mark topics as solved?

Hi Anh,
Please note a comma is missing on line 6 and there's an extra comma on line 10.
Line 39 has an extra trailing "s" on the plug-in name (meta-box/meta-box-include-exclude).

Once I fixed those typos, I was able to checkout the whole thing through composer. Then I added vendor/autoload.php to my custom plug-in and I get another issue: it will try to instantiate some classes twice -- one time from the standard wordpress plug-in and another time from my custom plug-in.

CMB2 does a smart thing in this: since it's thought to be bundled with themes and plug-ins, it will only load the most recent version of itself. I think you should consider implementing a similar check on each plug-in initialiser.

I removed the existing plug-ins, now I get this error:
Fatal error: require(): Failed opening required '/Users/mauro/GitHub/mundana_wordpress/wp-content/plugins/mundana-foundation/vendor/composer/../meta-box/mb-relationships/mb-relationships.php' (include_path='.:/Applications/MAMP/bin/php/php7.2.1/lib/php') in /Users/mauro/GitHub/mundana_wordpress/wp-content/plugins/mundana-foundation/vendor/composer/autoload_real.php on line 66

How do I fix this?