these aliases are missing: virgule cli_ure hwpfilter embeddedobj libxml2 unoxml
scp2 canvas cppcanvas slideshow help2

as discussed on our conference call yesterday, this is being tracked internally
in our issue 26661.

this partciular issue has come about after the modules patch was applied in
issue 26006.

updating whiteboard

reset prio to 1 as it is a data loss. if prio will be changed I expect a
reasonable explaination why.

Assigning back to Kenneth for further follow up.
Eric

reassigning back to support for tracking.

Our engineers are in the final processes of testing the functionality that would
enable OOo to submit module patch files to us as they did pre-upgrade to 2.6.

When they have completed testing on stage, and assuming things are fine, they
can roll the changes out to the live site. Once that is complete, we can restore
the 1.13 revision of the modules file. 

I will update this issue later in the day with the results of the engineering
testing progress.

updating whiteboard with additional internal issue number for tracking

I should add that I have an issue in the operations queue currently (26899) to
have the 1.13 version restored now while the testing is going on so you don't
have to wait for everyone to finish. If need be, I can refer to my internal
issue should tings go awry later.

the 1.13 version of the file has been applied. 
Lowering priority as we proceed with other testing.

The testing on stage went well, I'll find out today a timetable on making the
changes to the live site.

*** Issue 26006 has been marked as a duplicate of this issue. ***

2 quick updates-
1) the testing is proceeding along nicely, although it's not officially finished
(yet). I hope to have a timeframe tomorrow after speaking with the engineers and
Drew about when we can roll this functionality out to the live site.

2) I lowered this issue to a p2 because I felt that we had taken care of the
hottest, most urgent problem- applying the most accurate version of the modules
patch. As you know we've occassionaly had disagreements on the perceptions of
the prioritizations of the issues. Support normally considers p1 issues as a
site-down emergency or extremeley urgent issue. You can always comment in the
issue or email me privately if you believe the external issue priority shouldn't
be lowered. Fyi- The internal issue priority was never lowered.

In point #1 above, I mis-spoke/mis-typed. The testing was completed succesfully.
And the internal issue covering that was closed as resolved fixed. Sorry for the
miscommunication.

closing issue- the patch was applied and we've returned back to the old process
of submitting the occasional modules patch

close issue.