It was brought to my attention that the latest FM update (17.0.4) has
broken one of my plugins (BookVars). It was working on 17.0.3, and after
the update it no longer loads.
It seems that Adobe released this update without notifying the community
(developers and customers) that the underlying FDK has been updated.
They apparently didn't even bother to release the updated FDK, until
after releasing the update. This is incredibly irresponsible. I think
that they don't realize that people use FrameMaker to do real work, and
by introducing an update that breaks their customer's workflow can have
a significant impact.
It is expected that a new version may (likely) require updates to
plugins, but not a minor update. This has happened once (maybe twice)
that I can recall in the past 30 years. Clearly, they don't learn from
their own mistakes.
Here's the discussion on adobe.com ..
https://community.adobe.com/t5/framemaker-discussions/framemaker-2022-update-4-disables-some-api-clients/td-p/14581374
If you're rely on any plugins from Leximation, do not upgrade to 17.0.4.
(I think this probably applies to most plugins, but I can't speak for
other developers.)
I wish I could say that I'm surprised about this situation .. but no.
All the best,
...scott
_______________________________________________
This message is from the Framers mailing list
Send messages to framers@lists.frameusers.com
Visit the list's homepage at http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com
