Hi Tony, Thanks for checking.
> On Oct 30, 2014, at 3:20 AM, Tony Atkins <[email protected]> wrote: > > Hi, All: > > Looks good on Chrome for Android. > > Cheers, > > > Tony > >> On Tue, Oct 28, 2014 at 6:19 PM, Obara, Justin <[email protected]> wrote: >> The wiki and mobile plugin should be configured and working now. Please try >> going to wiki.fluidproject.org on your mobile device to try it out. If there >> are any more issues please let us know. >> >> Thanks >> Justin >> >> > On Oct 22, 2014, at 6:26 PM, Gill, Avtar <[email protected]> wrote: >> > >> > My apologies, Tony. I just noticed that you were pinging me here :/ I'll >> > forward the logs once I return from vacation next week. >> > >> > I wanted to point out that the Fluid wiki is now using Confluence 5.6.3 >> > and I briefly tried the mobile interface on an Android phone. We are >> > waiting for a license for the 'HTML for Confluence'* plugin that some of >> > the content relies on. Until we get that license the "Unknown macro: >> > {html}" text along with markup is being displayed on pages. >> > >> > Avtar >> > >> > * https://marketplace.atlassian.com/plugins/org.swift.confluence.html >> > >> > Excerpts from Tony Atkins's message of 2014-10-17 02:37:26 -0400: >> >> Hi, All: >> >> >> >> When the dust settles, I would like to take a few minutes to leave a >> >> proper >> >> bug report on the problems we encountered, as it seemed the plugin was >> >> obviously trying and failing to deliver the content rather than delivering >> >> the wrong content. Avtar, can I get a copy of the >> >> atlassian-confluence.log >> >> file for yesterday? >> >> >> >> Thanks, >> >> >> >> >> >> Tony >> >> >> >> On Thu, Oct 16, 2014 at 4:37 PM, Obara, Justin <[email protected]> wrote: >> >> >> >>> I've disabled the current mobile plugin. There is no longer a mobile >> >>> theme for our wiki. We should look into Tony's other suggestions. I'm not >> >>> sure who currently manages the licenses, perhaps that's done by Avtar. >> >>> >> >>> Thanks >> >>> Justin >> >>> >> >>> On Oct 16, 2014, at 4:19 AM, Tony Atkins <[email protected]> >> >>> wrote: >> >>> >> >>> Hi, All: >> >>> >> >>> I didn't see any obvious fixes in the versions between what we're >> >>> running and 5.6 (the newest), but it may be worth upgrading longer term. >> >>> Shorter term, we should disable the plugin. >> >>> >> >>> As an alternative, there is another mobile plugin which is available >> >>> free for holders of open source licenses: >> >>> >> >>> >> >>> https://marketplace.atlassian.com/plugins/com.refinedwiki.confluence.plugins.mobile >> >>> >> >>> Whomever is our technical contact for our current license should be able >> >>> to get them to issue a license for the plugin with very little effort. >> >>> >> >>> Even if we don't use their mobile plugin, it's worth getting in touch >> >>> with the vendor, they are one of the big players in theming Confluence. >> >>> Theme plugin developers are well placed to provide assistive solutions >> >>> for >> >>> Confluence, especially those who are active in markets where >> >>> accessibility >> >>> is a requirement. I have heard that clients in Germany are staring to >> >>> pay >> >>> good money to contractors to ensure that their Confluence instances meet >> >>> accessibility requirements on a case by case basis. A general solution >> >>> would be a big selling point. Ideally there would be multiple vendors >> >>> to >> >>> drive the prices down and quality up, which is why I have been pushing >> >>> the >> >>> ideas with every theme vendor I know. There are some who are not making >> >>> deep enough changes to the Confluence UI to help, but others who are very >> >>> close to releasing a general solution. >> >>> >> >>> As an example, Communardo (a German Atlassian partner) is planning to >> >>> release a plugin that adds themes that meet at least the accessibility >> >>> requirements of their local customers in Germany (I suspect they would be >> >>> meeting EU requirements, but that's one of the questions I want to ask >> >>> them). They would like to demonstrate their work in progress on the 23rd >> >>> during the European afternoon. Let me know if you're interested in >> >>> attending and giving them feedback. >> >>> >> >>> Anyway, setting aside the longer discussion about Confluence >> >>> accessibility, I am happy to help with the current problem in any way I >> >>> can: disabling the plugin, documenting the problem, contacting support, >> >>> installing alternate solutions. If I can get access to the logs, I can >> >>> do >> >>> a lot to at least document the problem as a bug report or support >> >>> request. >> >>> Whomever is administering our instance, please feel free to get in touch. >> >>> >> >>> Cheers, >> >>> >> >>> >> >>> Tony >> >>> >> >>> >> >>> >> >>> On Thu, Oct 16, 2014 at 9:39 AM, Tony Atkins <[email protected]> >> >>> wrote: >> >>> >> >>>> Hi, All: >> >>>> >> >>>> This is a plugin that is bundled with newer versions of Confluence (5.1 >> >>>> and higher). We are a bit out of date, I suspect that newer versions >> >>>> are >> >>>> tested with a wider range of mobile browsers. Will do a quick bit of >> >>>> searching to confirm. >> >>>> >> >>>> For now, I understand that upgrading is a longer term process, and that >> >>>> we need an immediate solution. The plugin can be trivially disabled by >> >>>> an >> >>>> admin (just search for mobile in the "add ons" control panel). Happy to >> >>>> assist if it's not clear to whomever is working on this. >> >>>> >> >>>> Cheers, >> >>>> >> >>>> >> >>>> Tony >> >>>> >> >>>> On Wed, Oct 15, 2014 at 3:31 PM, Steven Githens <[email protected]> >> >>>> wrote: >> >>>> >> >>>>> I think it’s the mobile plugin. When you search for the wiki on say, >> >>>>> mobile safari, the top hit is the wiki with a path of >> >>>>> /plugins/mobile/servlet/ something something something. If you manually >> >>>>> type in the wiki url so that mobile plugin version doesn’t get moved >> >>>>> to the >> >>>>> top of the hits the regular page works fine. >> >>>>> >> >>>>> Maybe we can uninstall or upgrade whatever plugin that is. >> >>>>> >> >>>>> -s >> >>>>> >> >>>>> On Oct 15, 2014, at 9:27 AM, Obara, Justin <[email protected]> wrote: >> >>>>> >> >>>>>> Hi Colin, >> >>>>>> >> >>>>>> I tried today. Got that error. Hit the retry button I think and now I >> >>>>> don't see it anymore. Not sure what caused it though. >> >>>>>> >> >>>>>> Thanks >> >>>>>> Justin >> >>>>>> >> >>>>>> On Oct 15, 2014, at 9:17 AM, Clark, Colin <[email protected]> wrote: >> >>>>>> >> >>>>>>> Hi All, >> >>>>>>> >> >>>>>>> When you visit the Fluid Project wiki on a mobile device (like an >> >>>>> iPhone), you get an error page saying "Oops! Something went wrong." >> >>>>> It's >> >>>>> been like this for a while, and I'm not sure what is causing it. Can we >> >>>>> look into it and see if we can fix it? A lot of users have been >> >>>>> complaining >> >>>>> recently. >> >>>>>>> >> >>>>>>> Colin >> >>>>>>> >> >>>>>>> --- >> >>>>>>> Colin Clark >> >>>>>>> Lead Software Architect, >> >>>>>>> Inclusive Design Research Centre, OCAD University >> >>>>>>> http://inclusivedesign.ca >> >>>>>>> >> >>>>>> >> >>>>>> _______________________________________________________ >> >>>>>> fluid-work mailing list - [email protected] >> >>>>>> To unsubscribe, change settings or access archives, >> >>>>>> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work >> >>>>> >> >>>>> _______________________________________________________ >> >>>>> fluid-work mailing list - [email protected] >> >>>>> To unsubscribe, change settings or access archives, >> >>>>> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work >> >>>>> >> >>>> >> >>>> >> >>> >
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
