>
> Anyway, if you want to disable them, just set $smwgInlineErrors = false;
> in
> your LocalSettings (after including SMW).
>
OK, will do, this might be a good idea for production site.
Although warnings are useful and maybe moving them to Factbox instead of
completely disabling is better - I'd vote for this functionality along with
configurable display of Factobox discussed before.
Sergey
On Nov 7, 2007 1:20 PM, Markus Krötzsch <[EMAIL PROTECTED]> wrote:
> The warnings are embedded in a way that allows clients without JavaScript
> browsers to read them. This of course involves Google's crawlers. I also
> wonder why the warnings are really a problem in Google, since they should
> be
> rare in general (their very purpose is to help people to spot errors
> quickly
> and fix them right away). If you write something erroneous into your wiki,
> there is always a chance of Google indexing it without you being able to
> propagate the fix to Google's caches right after spotting it.
>
> Anyway, if you want to disable them, just set $smwgInlineErrors = false;
> in
> your LocalSettings (after including SMW).
>
> -- Markus
>
> On Mittwoch, 7. November 2007, Sergey Chernyshev wrote:
> > Yes, it's possible to change a skin to output some description, but I
> > really want it to output page's content, not some generic words
> therefore
> > it's not that easy to achieve in wiki.
> >
> > When I was talking about JS, I meant that page will contain empty span
> tags
> > like:
> >
> > <span id="warning1"></span>
> >
> > and some JS code next to factbox will contain actual warnings so they
> could
> > be enabled/disabled with a button or with user preferences. It'll also
> > allow showing warnings in factbox itself.
> >
> > Sergey
> >
> > On Nov 7, 2007 1:42 AM, S Page <[EMAIL PROTECTED]> wrote:
> > > Sergey Chernyshev wrote:
> > > > It seems that inline warnings are being crawled and indexed by
> Google
> > > > which is quite bad.
> > > >
> > > > Here's home Google listing for one of my pages looks:
> > > >
> > > > *JavaScript: The Good Parts* - Technical Presentations
> > > > <http://www.techpresentations.org/JavaScript:_The_Good_Parts
> >
> > > >
> > > > warning.pngSorry, URIs from the range
> > > >
> > > > "http://www.techpresentations.org{{#mediapath:*JavaScript*<http://www.techpresentations.org%7B%7B#mediapath:*JavaScript*>
> <http://www.t
> > > >echpresentations.org%7B%7B#mediapath:*JavaScript*>*The Good
> > > > Parts*.jpg}}" are not available in this place. *...*
> > > > www.techpresentations.org/
> > > > <http://www.techpresentations.org/
> >*JavaScript*:_The_*Good*_*Parts*
> > > > - 18k -
> > > >
> > > >
> > > > I fixed the error and google is probably going to update it
> eventualy,
> > > > but still, it's not very good idea to have embedded HTML in there -
> > > > maybe it's better to have them inserted using JS instead... it might
> > > > help with enabling/disabling it on per-user basis as well.
> > >
> > > You might be able to use the googleoff/on comment tags. You want to
> > > turn off snippet and index, but you can probably just turn off
> > > everything with
> > > <!--googleoff: all-->
> > > warning HTML stuff
> > > <!--googleon: all -->
> > >
> > > Details at
> > > <
> > >
> http://code.google.com/apis/searchappliance/documentation/46/admin_crawl/
> > >Preparing.html#pagepart
> > >
> > > This definitely works for the Google Search Appliance, but I can't
> find
> > > conclusive evidence whether Google's own Web crawler respects these
> tags.
> > >
> > > Google tries to be smart about what to display in snippets, I'm not
> sure
> > > what heuristics work these days to discourage it. Try looking at
> > > Google's cached version of your page for clues. With JavaScript
> > > enabled, the SMW warnings are surrounded by <span style="display:
> > > none">, but the Google crawler sees the page with the warning in a
> > > regular <div>.
> > >
> > > <
> > >
> http://googlewebmastercentral.blogspot.com/2007/09/improve-snippets-with-
> > >meta-description.html
> > >
> > > suggests you can control the snippet using a
> > > <META NAME="Description" CONTENT = "blah blah" /> tag, you might be
> > > able to change your skin to output something here.
> > >
> > > You can turn off the snippet altogether with
> > > <META NAME="GOOGLEBOT" CONTENT="NOSNIPPET"> ,
> > > see <
> http://www.google.com/support/webmasters/bin/answer.py?answer=35304>
> > >
> > > --
> > > =S Page
> > >
> > >
> -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems? Stop.
> > > Now Search log events and configuration files using AJAX and a
> browser.
> > > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > > _______________________________________________
> > > Semediawiki-devel mailing list
> > > Semediawiki-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
>
>
>
> --
> Markus Krötzsch
> Institut AIFB, Universät Karlsruhe (TH), 76128 Karlsruhe
> phone +49 (0)721 608 7362 fax +49 (0)721 608 5998
> [EMAIL PROTECTED] www http://korrekt.org
>
--
Sergey Chernyshev
http://www.sergeychernyshev.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
