I see it’s over 500 days since I posted anything here.
One of the main reasons I haven’t posted is that software of late has become remarkably stable and I just don’t seem to be coming up against problems these days.
I recently set up Matomo Web Analytics on a server. One of the many reasons I did this was to compare traffic over several sites. I run quite a few sites both for myself and for others and wanted to see if there were any sites that could be culled. To my surprise, this site is still getting visits: nothing hectic but it is still active, and is by no means bottom of the pile.
The majority of visits seem to be concerned about the Iomega iConnect which is a piece of kit which has long vanished off the market. It was always very problematic and my one is now gathering dust on a shelf somewhere. Obviously others are still using it and by the sound of it, still having problems.
The majority of other posts are mainly concerned with issues I had found in previous versions of Linux Mint or WordPress. Over time these issues seem to have been resolved, but presumably people are still running older versions of Mint (or WordPress) and are still coming across those problems.
So the question is whether or not to consign this site to history. I originally set it up as a sort of reference notebook for myself which I could refer to if a problem reoccurred. I haven’t used it for that purpose for a very long time.
I am a great fan of Weaver Extreme and its almost limitless variables and customisations.
One problem that irritated me though was the Info Bar, and in particular the Breadcrumbs.
Example 1 => Home→Books→Short Story Collections→Blackjack
To my eye, that looks cramped. I needed a space each side of the arrows. I tried a load of things such as trying CSS, searching forums and anywhere else I could think of. No one else seemed to have the same problem.
Eventually I resorted to the sledgehammer approach: I changed the coding within Weaver. I don’t like doing that as it has to be redone in the event of an update.
The file is “themes/weaver-xtreme/includes/lib-runtime.php”.
The line to be changed ( search for ‘weaverx_breadcrumb’ ) is
One of the little add-ons for Thunderbird that I like is FireTray.
It’s that little mail notification icon on the task bar that turns into a number when an email arrives and it dispenses with the need to keep checking Thunderbird to see if anything new has arrived.
With the latest release of Thunderbird, FireTray no longer worked. There was no warning – it just failed to appear. As a result I kept missing urgent emails because I wasn’t used to constantly flicking into Thunderbird. I checked Thunderbird’s Add-on area and it merely confirmed that FireTray was incompatible.
I tried the repositories but with no success, but then came across the solution.
Then in Thunderbird, select Tools -> Add Ons. In the window that opens, click on the cog [top right corner] and select “Install Add-On from File” and select the file you have jut downloaded. That will install the updated FireTray.
I run a couple of WordPress sites that contain IFRAMES.
The problem I had was that the content of the IFRAMES wasn’t updating when a visitor arrived at the site. They would see content that was hours or even days out of date.
In each of my sites I was generating files which updated every ten to fifteen minutes. This was done using a small programme that I wrote which generated small HTML files on the site itself. The IFRAME was then used to display that HTML file. However, caching in the site prevented that and insisted on dishing up a cached version which was out of date.
I took a two pronged approach.
The first objective was to tell the IFRAME to load a different filename each time the page was loaded. Obviously I couldn’t rename the origin file, so I added a parameter to the file request in the form “file.htm?t=X”. Now X had to be different each time the page was loaded so I had to enable PHP on the page and then create a timestamp date(“U”) so that X would change every second.
This will force the IFRAME to search for src=”/file.htm?cacheN=1534593560 or similar where the number changes every second. The parameter “cacheN” will be passed to the file but as it is meaningless it will be ignored and file.htm will be loaded.
Naturally to run PHP on a WordPress page will require a plugin or a facility within the theme being used.
The second method I used (a belt and braces approach) was to add a line to the head of the page (which can either mean another plugin or manually editing your theme’s header.php file)