However, since some time the search does not return any result.
Is there a new setting that should be set?
Is it because I used to demo it in MM15 and just last week I used it with MM16?
NOTE: The Amazon and EBay webservices are functioning as usual.
For now, my temp solution of doing the search in google and pull the results page in the mind may work as a short fix.
I am frankly shocked at how a feature which has worked (albeit imperfectly) in MindManager since at least version 8 or 9 should suddenly stop stone dead.
I use the search part frequently in my work and it is also an essential tool in researching for my blogs. In fact I wrote a post on how to make best use of the Google search part, though this appears to be redundant now.
I have just tested the search part in versions 11, 12, 14 and 15 as well as 16 to confirm that it isn't working in any of them. Clearly therefore this is not a bug in MM 16 itself but is somewhere in the back end, which makes me wonder if this is some sort of licensing issue between Mindjet and Google (like the problems with Adobe over PDF printing).
Irrespective of what the problem is or which version or versions are affected, if the answer that Jerry reported from tech support is correct, it is also extraordinary that Mindjet would state that the response to the sudden failure of a feature in the current version is to wait for, and be forced to upgrade to, a new version which hasn't appeared yet. That is akin to saying that if the heater in my 2016 Subaru has suddenly stopped working the only remedy I have is to wait for - and buy - the 2017 model.
Not good enough Mindjet. Not nearly good enough.
I would agree, to have this feature in failure mode does not speak well for Mindjet.
Let's hope for a solution sooner than later.
- what caused the problem;
- confirmation that the problem will be resolved in the upcoming release of V17 of MM;
- an indication whether a patch will be released to fix the problem in existing versions of MM, at least V15 and V16;
- whether there will be any improvements to the basic functionality of the Google search map part when it is restored, given that it hasn't been updated since at least V9;
- some sort of commitment that there will be better communication with MM users around these sorts of issues, should they occur again in the future.
Apologies for the delay in posting an official reply on this thread. It is true that Google has deprecated the API that was used in MindManager for the Google Search Map Part. We researched our options and concluded the Map Part would be to be completely rewritten using Google's new API. As a result, we have decided to pull the current Map Part from the upcoming release of MindManager 2017 (Fall 2016 timeframe) and will not be releasing a patch from MindManager 16 and earlier versions.
As Alex Gooding mentioned above, the Google Search Map Part has remained unchanged since it was first introduced in MindManager version 9. I am starting a new Idea thread How Would You Improve Google Search in MindManager and would love to hear your suggestions.
When replying to the Idea thread, please provide -
- Your use case (business or personal) with using the Google Search Web Part.
- How can it be improved? (i.e. include images?).
Thanks Marian for posting this response and explaining the situation, as well as for the initiative to seek feedback on what an ideal Google search part would look like.
I understand that from time to time changes in third-party products over which Mindjet has no control will affect features in MindManager and other MJ software. If and when this occurs in future however it would be helpful if Mindjet could be more proactive in identifying the problem and announcing what it is going to do in response.
Also, correct me if I am wrong but I understand that the deprecation of this feature was something that Google had actually signalled well in advance. If this is the case I'm surprised that Mindjet is only now responding to the problem.
Further to my earlier post I want to echo Jerry's concerns.
I am shocked and dismayed that there won't be a fix even for version 17. The Google map part is a critical research tool for many users including me - I use it frequently in my consulting work and blog writing and have developed and written up a detailed range of techniques on how to maximise its use. A potential delay of 15 to 18 months in releasing a rewritten Google map search part is simply unacceptable, especially if my suspicions that Google provided plenty of warning of the deprecation of the search API are correct.
I also second Jerry's request that a patch which replicates the basic functionality of the current map part be released much sooner. At the very least a basic rewritten map part should be incorporated into V17 or if this really isn't possible in the available time then it should be released as soon as possible as a point upgrade to version 17.
Jerry, I'm not sure of the exact date but your research has confirmed my suspicions based on some of my own digging around. Clearly, Mindjet should have had ample warning that the deprecation of this feature by Google was going to occur.
If this is correct then there are two alternatives, both equally disturbing:
- There was some sort of comprehensive systems failure at Mindjet which somehow allowed news of the deprecation to slip by unnoticed over the past six years; or
- Senior management were actually aware of the looming deadline for deprecation but for whatever reason decided not to address this problem.
If the latter point is closer to the mark it leads to suspicions that despite the request for input on how to redesign and improve the Google map part it may never be restored for technical or other reasons, especially if there is little "evidence" that people are really using it. I'm afraid that Mindjet have form in this regard; there have been other features that the company has tried to dumb down in previous versions (for example, in version 9 the attempt to remove the ability to send multiple appointments from MM to Outlook), supposedly based on research which shows these features are not used by the majority of users.
My disappointment is Mindjet could have saved everyone some time by writing for the new Google API before the release of Mindjet 2016. With well over two years lead time, there was not need for this current problem. I suspect, the writing team figured time was on their side and they would have more time to address a known flaw in the current release.
My current concern is how many other problems are in the current release that will fail in the future? Are the other search engine released notices on their APIs (amazon, eBay)?
I would like to see Mindjet provide full disclosures so I can plan how I use the product. I don't want to utilize features that are going to fail in the very near future. Also, I want to see bug fixes that are provided in no less than 90 days. I don't want to wait for a new product release with the existing feature removed.
I look forward to a better solution than currently proposed for this situation. I really want to see a bug fix issued in no less that 90 days.
Finally, while a few people may engage in this conversation, Mindjet should remember, people who don't share their thoughts on this board can often find their solutions through other boards or products. I would encourage Mindjet to take this problem seriously.
Since I have long ago given up hope that Mindjet cares about the user community I needed to develop a workable solution. Below is an image of my workaround. Elegant - NO, but at least it works. Just the thought of editing my thousands of search map parts is overwhelming.
I have a feeling I will have passed on to the next world before Mindjet fixes this. When (if) they do, it will charge me way to much money.
Bitter, yes, understanding, no!