These are chat archives for gantry/gantry4
checkBrowser()method. Since that method is pulling from the user agent it should not be effecting the browser version detection.
checkBrowser()method adds detection for Edge and fixes some issues like links coming from Office documents.
$version = explode(' ', $result);)
$this->user_agent = isset($_SERVER['HTTP_USER_AGENT']) ? $_SERVER['HTTP_USER_AGENT'] : "undefined";
@photodude could you please elaborate a little further about this
The only thing I have left on my list was related to the 2015 Google bot change to start indexing css and JS which were blocked by Joomla's default robots.txt file since they were not located in the media folder,
Basically asset files should be located in the /media/[your library or extension] folder within Joomla after install.
I've been ignoring that issue since I added lines to allow googlebot to index the asset folders located in the wrong locations (according to Joomla's 3rd party developer standards).
But for someone who hasn't made that change, google is penalizing them and reducing their SEO score.
@N8Solutions the PR for any changes related to this in Joomla that I knew of was killed to quote the closing statement "Closing this issue as the solution is basically in place, we should use the media folder for media."
In otherwords any component or library that doesn't follow the Joomla Development Best Practices Will still have this issue.
That is unless the site owner using those extensions have modified their robots.txt file to allow each and every exception for when a developer did not use the media folder.
Exceptions for gantry in the robots.txt were
Allow: /libraries/gantry/css/ Allow: /libraries/gantry/js/ Allow: /libraries/gantry/assets/jui/fonts/font-awesome4/
I saw a 3 line change for the robots.txt file which supposedly would allow for all .js and .css files, but I would still get errors in google webmaster tools using that supposed fix. I've found two solutions that are consistent in fixing this issue. Either Site owners have to use exceptions route listed above, or developers need to follow the Joomla Development Best Practices and place their assets in the media folder.