Moodle 2.9.4+ (Build: 20160218) (very recent update - just a few days ago, from 2.9.1+)
I only noticed this today, so I can't pin it directly to the above referenced update or recent Atto additions.
Atto is misbehaving, but not in all modules. The behavior is:
- Applying formating to text that is not selected.
- Inserting hyperlinks as the actual URL - linked - rather than linking the selected word or image
If I enter the following text in the Page content box of Page module and select the text to bullet (One Two Three):
It becomes this:
It seems to always apply the bullet to the last item on the page, even if it is an image.
Trying to make the word "Google" into a hyperlink yields this:
The link appears as text of the URL, linked. Somethimes it inserts it in the middle of the text selected, like "Goohttp://www.google.comgle.
I have begun uninstalling recent Atto add-ons:
Wordimport - uninstalled through Moodle admin, then deleted directory from server. Purged caches.
Did not solve problem.
Have recently also installed Chemistry, Matrix, and Computer Science add-ons -and a few others weeks and months ago.
I will start uninstalling the add-ons, but wanted to go ahead and get this posted, in hopes of time-saving advice from the community!
I am doing all of this uninstalling and testing on our test server, but the problem is occuring on our production servers (2). I did install the add-ons mentioned on the test server and tried them out for a few days first with no problems. They were all installed before the upgrade to 2.9.4.
Debugging is turned up all the way, but not errors reported.
And the behavior is not consistent across all instances of Atto. The problem doesn't occur in the body of a test question, but it does in the answer choice and feedback boxes. It occurs in Page, as described above, but not in Book.
I have restored the Atto tool bar settings to their default, but have only uninstalled Wordimport.
Our server guy did have to enable the XSL extension on the test and student production server, but the problem occurs in our Professinal Development instance where XSL was already enabled.
Any help would be greatly appreciated!