Hi Michael
Unfortunately, you haven’t asked the most important question:
Are both plugins GPL 2+, GPL 3+ because if that would be NOT the case it would NOT be possible to integrate it into a WP site and sell it to i.e. customer as a complete work while the customer could integrate it afterward by himself or additional costs by us of course, As both plugins actually rely on the WordPress core functionality both would need to be (a must) GNU GPL 2+/3+ according to the WordPress GNU GPL License.
We tested the plugin already in its free version, but as we build 100% on WordPress GNU GPL 2+ License for our customers we also guarantee them that the work itself is GNU GPL 2+/ GNU GPL 3+ which would not be the case when we integrate code which has not a GNU GPL or compliant license.
You are right that the plugin offers lots of features. The pro version even more additional codes from external vendors like Google etc. and some additional texts to the licenses which are actually part of public spaces too. So really new is the integration which follows the examples which have been given in the free version. The code is working, even it is not as easy to read as better other structured plugins, functionality is important in that case and that is given. That is also the reason we posted that in a reply to a 5-star review. We will write our own review if we have all questions answered.
I did post the question twice as it did NOT appear at the review of @mischaef and we had to assume that censorship took place. Unfortunately, pretty common our days in the review business. And unfortunately, we can’t test the pro version with the map integration, so we rely entirely on the demo on your site.
2 points we need a clearer view right now – summarised:
1. What license is the Pro-Version – is it GNU GPL 2+/GNU GPL 3+ like the Free version you have on the WordPress repository and do we need to install a new plugin with new plugin name and new namespace or will it be only entering a license number?
2. We saw the google map and open street view as well as other integrations that show only a black placeholder instead of an image i.e. a screenshot of the map or the “online resource” which should load after excepting the specific resource. The idea is great but the look with a black space is terrible. Until now we replace that space with an image (i.e. of the static map) and sometimes even with 2 switchable images of the actual map and the satellite image and when people click to verify to use the online service they can click a link to accept and get directed to the actual online map view. This also helps us to reduce the usage of Google Maps API which on high traffic sites can cause lots of costs (i.e. if you run a directory where always a map view gets loaded, only to display the site. Since we do that replacement we have about 60% reduction of costs to Google because most visitors are actually happy with the static map view and don’t require to use the Google API. So our question would also be if it is possible to limit the use of the map only on a specific page – as each new page would be another API call to Google. This sums up pretty fast in directories. If now the user has to accept to see a specific map live on each page it would be just fine and reducing costs tremendously, while when you accept one time their cookie it would always be accepted on all directory entries would cost a huge rise of costs.
Thanks!
-
This reply was modified 4 years, 6 months ago by toremo.
-
This reply was modified 4 years, 6 months ago by toremo.