SilverWav's Journal

The best is yet to come…

Support

with 12 comments

If you have any ShelveLogger.html related issues report them here.

Written by SilverWav

March 14, 2010 at 11:11 pm

12 Responses

Subscribe to comments with RSS.

  1. I am esting a new footer template today I noticed the %D works but %{date} causes an alert error message and evaluates to empty value. All the other longnames I used were ok. My test template is:

    Year
    %Y
    %{fullyear}
    Month
    %M
    %{month}
    Day
    %D
    %{day}

    Only %{day}% causes error message. Can you reproduce this?

    Platform: Win 2k sp4/ffx 2.0.0.20/shelve 1.19

    Scott R

    April 29, 2010 at 5:03 am

  2. Hi Scott R,

    I would suggest updating to the latest shelve 1.22 from here:
    Shelve 1.22 first.

    If that does not solve the issue notify the developer on the Shelve Suport Group here:
    Shelve Firefox Add-on.

    Note: I don’t actually use the footer feature of Shelve in ShelveLogger.

    SilverWav

    April 29, 2010 at 8:27 am

  3. Can any information be provided with respect to the problem outlined in the following thread?

    http://groups.google.com/group/shelve-firefox-addon/browse_thread/thread/4b28171c87b93b21#

    I have noticed that using the ShelveLogger “profile” with Auto-Save (Web page complete, HTML only) results in a very significant slowdown of the browser and host once a few pages have been saved to a given log file… The behavior has been observed under Windows, OS X, Solaris and on local as well as cloud-based (EC2) hardware…

    Rishi Chopra

    March 5, 2012 at 12:40 am

    • Looking at the thread I see a reply from lith
      “Hi,

      I currently have no time to look into this.

      Since shelve’s main use case is to manually save a document, performance wasn’t a top priority. I never found shelve’s performance annoying though.

      Does the problem persist when

      – when changing the file format to plain text,
      – when using a vanilla profile with no other addons installed, or
      – when switching of writing to the log file?

      though performance when the plug-in was first installed was also impacted (i.e. degraded) and is reminiscent of what I observed when running Slogger on Windows XP and Linux hosts.

      Could you please explain/describe your observations in greater detail. ”

      I would advise replying and answering his questions.

      SilverWav

      March 6, 2012 at 7:31 am

      • Please note that the thread which was referenced on 03/05/2012 has been updated; in short changing the way Shelve auto-saves pages seems to have solved the problem… but the fact that such a change can make such a dramatic difference in UI responsiveness probably merits some sort of documentation independent of the referenced thread (maybe near the “Use with this template:” section in the HTML file?)…

        Rishi Chopra

        March 18, 2012 at 5:12 am

        • Thanks for the information.

          I’m glad that that you have been able to resolve this.

          SilverWav

          March 18, 2012 at 8:50 am

  4. I have a bunch of shell scripts that manipulate slogger log files. I’d like to switch to ShelveLogger but I’m having difficulty configuring it so as to create log files that are indistinguishable from those produced by slogger. The ShelveLogger files contain an embedded style sheet whereas I’d prefer to use the external ‘slogger.xsl’; and they include a chunk of JavaScript that prevents the HTML being interpretable as XML and which I do not need in any event. Both components are, presumably, being copied into new index files from somewhere. But I can’t seem to find the sourcefile or the code that does the copying. [I’m running Linux.] What am I missing here?

    Geza

    October 13, 2013 at 11:22 am

    • IIRC I think I took the my old slogger files and used AWK to update them to the Shelve format… but it was a long time ago.

      You could try the defaults in Shelve first as I think the author includes a simple version of ShelveLogger by default.

      I think there was a lot of correspondence between the Shelve Author and I that I saved in my Google groups…

      I will try and dig it out… my god where does all the time go to?

      Found it :-)

      https://groups.google.com/forum/#!topic/shelvelogger/J2zPDDsgsb0

      https://groups.google.com/forum/#!forum/shelvelogger

      Hope this helps, have fun ;-)

      SilverWav

      October 14, 2013 at 12:34 am

      • Thanks for your prompt and helpful reply. I will go through the material you have dug up — it should help me understand what Shelve and ShelveLogger are doing. I definitely don’t want to convert my old slogger index files (of which there are more than 15,000) into files that contain CSS and JavaScript. From my perspective, the merit of the slogger index files is that they are pure data in an XML wrapper without any extraneous material. So I want to get as close to that as I can. I will report back in due course.

        Geza

        October 14, 2013 at 10:59 pm

      • I promised to report back in due course. 31st December was my deadline so, of course, I left matters until yesterday. The file containing the Javascript logfile prefix, log.html, was hiding in the shelve.jar file. So I added a new file, slogger.xml, containing the three-line Slogger logfile prefix XML code, to the jar file and invoked that instead of log.html. And then I changed the HTML table code in the Log section of the Shelve to XML that creates Slogger-like logfiles. I haven’t had much time for testing (yet) but this all seems to work with one residual problem. The XML logfiles created are ill-formed (and thus Firefox won’t render them) because they lack a closing sloggerLogFile tag. I can’t see any way to get Shelve to append this to the logfile. I can get round the problem with a clunky cron job that checks every night to see if all logfiles have the closing tag and adds it to the ones that do not. If any reader can think of a more elegant solution, then I’d be delighted to learn of it.

        Geza

        January 1, 2014 at 8:46 am

  5. Hi, this is a great tool, it works for most websites. However, when accessing webmails such as Yahoo! and GMX, it’s not working well. the logs act as real webpages. The first one just logs out immediately or says the session is expired and further navigation is not logged properly. I’ve got Shelve 1.34 and ShelveLogger 4.31, MIME option Webpage, complete (HTML)

    Seb

    May 28, 2014 at 12:42 pm

    • Yes web-mail pages are probably very java script heavy and so will not save well.
      ShelveLogger is really just for regular web pages.

      SilverWav

      May 28, 2014 at 5:29 pm


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: