My sites are set up and working fine with the free version TinyMCE 5 in the cloud. I guess it's their AWS.
Can we continue to use it even though version 6 was apparently released? If so, for how long? Do they leave their old versions up and available?
Right now I feel "if something's not broken don't fix it."
Thanks.
TinyMCE 5 will continue to work to past March 15, 2023 - You can see exactly which version in the TinyMCE 5 series is supported in the Tiny Docs page on Supported Versions. This way, you can plan out a timeline for migration: https://www.tiny.cloud/docs/enterprise/system-requirements/#supportedtinymceversions
If you'd like to try TinyMCE 6 to see what it offers, the new documentation for TinyMCE 6 is also ready: https://www.tiny.cloud/docs/tinymce/6/
Migrating to TinyMCE 6 is straightforward – it involves adjusting the cdn script for accessing Tiny in the cloud, and then checking for Plugin and Option names that have been renamed in the transition from Tiny 5 to Tiny 6. The Migration guide has all the information: https://www.tiny.cloud/docs/tinymce/6/6.0-release-notes-overview/#overview
Related
A day ago my prestashop website, in the comment box of the blog started to display the following message:
And entering the post that explains how to migrate the version of TinyMCE , I do not understand very well how to perform these steps in my prestashop.
How can I update this?a
if you are using a third-party module to make your blog it might be is including its own version of TinyMCE. You should try to dig in its code to understand that.
If this is not the case, the blog uses TinyMCE which is normally included in Prestashop core.
On said that, this second case is likely to be the one. Update the e-commerce unlikely will solve your problem. I honestly don't remember in which version they are with TinyMCE but doing an upgrade like that might break back-office editor forms so I don't think they are keen on that at the moment. They are doing a major rollover to Symfony, I am pretty sure this is their priority right now. As said in one comment, Prestashop's dev team has to solve the issue on their side.
Google Pagespeed is pointing out our tinymce.js for using dynamically injecting document.write() which can delay page load by tens of seconds.
We are using version 3.5.8 without customizations.
Any idea how to fix this?
Best regards,
Jane
TinyMCE 3.x has not been a supported/developed release of TinyMCE for years now so unless you wanted to attempt to modify the source code of TinyMCE yourself there is really no way to get this "fixed".
TinyMCE's current release is 5.6 so I would start by using the most recent release and seeing if that has any issues. If it does you can report them to TinyMCE at our GitHub Issue tracker: https://github.com/tinymce/tinymce/issues
Is it possible to activate, create a Definition-List in TinyMCE
"Definition list" is checked in TinyMCE Toolbar settings
plone.app.widgets 1.8
TinyMCE 4.x
Plone 4.3.4
I assume it did not work in your case? right?
First thing you try is to update to the moste recent compatible version for you Plone version and also update Plone 4.3.x to moste recent version.
Few weeks ago they released plone.app.widgets 1.9. They put a lot of effort into it to make it feel more like the Plone 5 version.
Update to Plone 4.3.10.
I have a Movable Type site running MT 4.38, and I was wondering whether I should upgrade to 5.
For a while, MT 4 and 5 seemed to have been developed concurrently, but now I only see activity in MT 5. Has MT 4 been abandoned?
The person using the site is change averse, so I only want to upgrade if it's absolutely necessary (i.e. security issues).
Thanks
Yes. Movable Type 4.38 has a patch for a security vulnerability which you should be sure to apply. But beyond that, you should absolutely upgrade to Movable Type 5.2.3.
The big reason is that Movable Type 4.38 will be end-of-lifed on December 31, 2013. This means that there will be no security updates for Movable Type 4.38 after that date.
Movable Type 5 has a number of great new features that are huge improvements over MT 4.38:
New and improved Rich Text Editor based on TinyMCE
Revision history on the most-used objects in the CMS
List-management framework enhances Movable Type's ability to manage large amounts of data inside the CMS
Sortable categories and folders
Template tags for things like mt:EntryPrimaryCategory
Enhanced multi-blog support
Huge support improvements for Webkit-based browsers (Safari and Google Chrome) as well as IE 8 and 9
Login failure detection, allowing either account or IP address lock out
With all due respect, no one should be running a version of Movable Type that is no longer supported with security patches. It's foolish to think that any one person can know all of the possible security issues in an older version of a Content Management System such as Movable Type.
Yes, MT4 is no longer developed. It still receive security patchs every few months, but there will not be a new version.
As for what you want to use, MT4 and MT5 have a different set of plugins. So if you want to upgrade, check that the plugins that you need support MT5 or have a MT5 replacement.
Upgrading would work without any problem if you are not using 3rd party plugins.
If you're using 3rd party plugins, you might encounter compatibility issues because the v5.x architecture is much different than 4.x.
Before considering to upgrade to v5.x you may like to check your 3rd party plugins and see if there is a version that works with v5.x.
Another thing to consider is to clone your installation and try to upgrade it on a different domain/folder or on a stage server where you could check that everything works before upgrading your live installation.
Alternatively you could order a professional movable type upgrade service from:
http://www.movabletypeupgrade.com/
I've been given a request to upgrade an application running under filemaker pro 6.5.
It's connected to some serial devices and uses plugin-component (troi) to solve the communication (rs232).
It's running in a closed network attached to a remote FM65-database.
Will FMP12 be able to run the application w/o a lot of recoding or has things changed too much?
Regards,
/t
Simple answer, yes.
First of, there was no FileMaker 6.5. It went from version 5 to 5.5. to 6 and then 7. When version 7 was released there was a major update in fileformat for the databases, introducing multiple tables in a singel file and a new relationship schema.
Between version 11 and 12 there was another big update in fileformat. The bigest change being that the layouts are now rendered as HTML/CSS using WebKit.
Even though a lot has happend since version 6 FileMaker Inc always try to be backward compatible. As far as I know, no functionality has been removed, at least nothing vital.
Troi Serial Plugin works with FileMaker 12 but you will need to upgrade the plugin. you can read more about the changes for the plugin, pricing and download a demo at
http://www.troi.com/software/serialplugin.html
You can also download a 30 day trail of FileMaker from http://www.filemaker.com
Thus you can easily try the entire setup for free before doing it for production.
The only thing you probably will have to adjust is the function call for the plugin Troi Serial, but that should be easy!
Hope this helps
I'd recommend you use Metadata Magic to analyze the FP5 solution.
There are some script steps that can be problematic when upgrading. This will give you a comprehensive report of what issues to look for and where to find them. It's not uncommon to find script steps that need to be reordered or changed.