Hello Lester Caine Hope you are well. Have you had time to apply your expert skillset looking at the ticket? Your skillset turned out to be critical in fixing the subdomains, we owe you many thanks for that, and truly hope you can continue your work and look at the but report (bug#66371) which claims an error in the typeahead javascript.
-Hannes On Sat, Jan 11, 2014 at 1:10 AM, Hannes Magnusson <[email protected]> wrote: > I can't write much from the hospital on my phone but from the sound your > valued feedback everything has been fixed now on all subdomains. > > Could you go back to the original bug report about JavaScript error in the > search box? > Your expertise is critical in resolving that issue. > > -Hannes > > On Jan 10, 2014 11:06 PM, "Lester Caine" <[email protected]> wrote: >> >> Hannes Magnusson wrote: >>> >>> I have committed a potential fix to the shared repo. This >>> automatically update all the subdomains you just pointed at. >>> >>> Can you confirm this is fixed (could take up to 40minutes to update >>> all the domains)? >> >> >> That at least make the sites usable, but I'd simply assumed that since the >> main site was using bootstrap it was used because it SHOULD care of all >> browser variations. Bootstrap dropping IE7 support from BS3 was the last >> straw in my trying to make it actually work, and when I switched to 'ink' >> but that has similar problems with IE7 :( >> >> What should have been discussed when adopting a new framework was what >> would be broken. One major reason for leaving the legacy framework working >> is to support that minority who for what ever reason are still stuck with >> legacy hardware? I still can't see why we can't maintain legacy.php.new. >> However I can now see that the structure of the 'website' is considerably >> worse than I had expected. Content should be managed in a way that can be >> backed up, translated, and mirrored independent of the display framework. >> This can then provide a clean basis to provide translation layers. Something >> which is currently missing from 'wiki' and now prevents the creation of a >> clean 'search' facility for the whole site. This was one of my design goals >> over 10 years ago but I'm even further from a working system now than I was >> then! Sites which provided all this transparently 5 years ago have been >> broken by the changes to PHP :( >> >> I'm still stuck a bit at the first hurdle with my own sites. One has to >> ignore IE7 in some instances when dealing with complex multimedia, but even >> these should have a clean fallback. Bootstrap has abandoned that as too >> difficult and so have many other sites, but PHP does not have anything >> currently which needs the stuff that only works on the latest browsers. I >> can't see why the main site should have any problem with javascript other >> than javascript is required to make bootstrap work at all, and the order of >> loading is important. Why is bootstrap needed on the main site when it's not >> used on the sub-sections? That was the main jist of my not wanting to 'fix' >> it ... removing it IS the fix going forward! >> >> -- >> Lester Caine - G8HFL >> ----------------------------- >> Contact - http://lsces.co.uk/wiki/?page=contact >> L.S.Caine Electronic Services - http://lsces.co.uk >> EnquirySolve - http://enquirysolve.com/ >> Model Engineers Digital Workshop - http://medw.co.uk >> Rainbow Digital Media - http://rainbowdigitalmedia.co.uk >> >> -- >> PHP Webmaster List Mailing List (http://www.php.net/) >> To unsubscribe, visit: http://www.php.net/unsub.php >> > -- PHP Webmaster List Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
