The Gorse Fox is still going. He had no idea how much raw video footage he had. He started the day by wondering if there was some way to easily embed the videos in his private (Wordpress) blog. Certainly, it should be possible, but as far as using a player within Wordpress to play a video served by Plex, seems beyond the wit of the Gorse Fox at present. Then he thought about Plan B. What about linking directly to the NAS and playing it? It should be easy enough, but at this point, he still hasn't cracked it. What he doesn't want to do is to upload the videos as media into his Wordpress server and thus duplicate the storage. This will have to sit on the back burner for now.
Giving up, he returned to DaVinci Resolve and the task of editing individual videos from the huge forest of raw footage. Three more videos have been completed for events in 1990 and 1991.
Meanwhile, downstairs the Gorse Fox can hear the Silver Vixen's sewing machine or overlocker humming away as she works on new outfit for Ellie.
Showing posts with label Wordpress. Show all posts
Showing posts with label Wordpress. Show all posts
Saturday, June 06, 2020
Thursday, April 18, 2019
Success
Well another fabulous day. Temperature in the low 20s and very little cloud.
Cousteau-Cub is on her way and it looks as if she has just touched down in Moscow at the end of this leg of the journey. Her next flight is in a couple of hours and should take her to Amsterdam.
We've had a quiet day punctuated by a quick trip to the farm shop to review various cat food options for Jasper. We came away empty handed but will check online for the recommended stuff.
The Gorse Fox has received a further email from the developer of the plug-in for WordPress. This gave the final clue that seems to have cracked the problem. It took a little fiddling about, but now he can link directly to Google Photos galleries from inside his private blog. He is going to leave it for 24 hours to make sure no tokens get revoked, and that the photos still display tomorrow... but if everything is ok, then he will implement the code in the production version of the blog (at the moment it is only in the test version).
Cousteau-Cub is on her way and it looks as if she has just touched down in Moscow at the end of this leg of the journey. Her next flight is in a couple of hours and should take her to Amsterdam.
We've had a quiet day punctuated by a quick trip to the farm shop to review various cat food options for Jasper. We came away empty handed but will check online for the recommended stuff.
The Gorse Fox has received a further email from the developer of the plug-in for WordPress. This gave the final clue that seems to have cracked the problem. It took a little fiddling about, but now he can link directly to Google Photos galleries from inside his private blog. He is going to leave it for 24 hours to make sure no tokens get revoked, and that the photos still display tomorrow... but if everything is ok, then he will implement the code in the production version of the blog (at the moment it is only in the test version).
Monday, April 08, 2019
1900 lines
Well that's it. It is done. More about that in moment.
It was late start to the morning for the Gorse Fox... nearly eight before he woke up. On a work day too! Oh no, he lies... it's not a work day. Retirement is such a pleasure.
There were some domestic chores to get out of the way first thing, but they didn't take too long and all the floors are gleaming again now. Then there were several phone calls to complete. One to the airline regarding access to the planes - now sorted; and one to the Travel Insurance company.
The thing about insurance, and travel insurance is a case in point, is that the insurers seem to find so many ways to avoid paying out. With travel insurance, the common get out clause is regarding medical conditions. It is not really a matter of whether the condition is relevant to your claim, it is the fact that you went to the doctor for some treatment and didn't inform them. The Gorse Fox was not going to fall foul of this so called up and informed them of anything in which they might have an interest. To be fair they asked if anything was relevant when we actually booked the holiday - and the Gorse Fox said no, it's been booked for a year now. They said it was no problem - we're fully covered as we were unaware of any conditions when the holiday was booked. Fair enough.
Back to the code. It has taken over 1900 lines of code - none of which is likely to be re-used. The code now extracts and reformats all of the old Google Plus posts, links to any relevant photos (where Google actually extracted them), and embed any check-ins or maps. The second stage of the code runs through the extract and plugs the relevant information into the databases. Et Voila... over a thousand new entries have been added to the test version of the private blog - and in 30 minutes time, they should similarly have been added to the production version.
There is some tidying up required where GPlus generated some daft titles or failed to extract the photos - but that can be handled over time.
It was late start to the morning for the Gorse Fox... nearly eight before he woke up. On a work day too! Oh no, he lies... it's not a work day. Retirement is such a pleasure.
There were some domestic chores to get out of the way first thing, but they didn't take too long and all the floors are gleaming again now. Then there were several phone calls to complete. One to the airline regarding access to the planes - now sorted; and one to the Travel Insurance company.
The thing about insurance, and travel insurance is a case in point, is that the insurers seem to find so many ways to avoid paying out. With travel insurance, the common get out clause is regarding medical conditions. It is not really a matter of whether the condition is relevant to your claim, it is the fact that you went to the doctor for some treatment and didn't inform them. The Gorse Fox was not going to fall foul of this so called up and informed them of anything in which they might have an interest. To be fair they asked if anything was relevant when we actually booked the holiday - and the Gorse Fox said no, it's been booked for a year now. They said it was no problem - we're fully covered as we were unaware of any conditions when the holiday was booked. Fair enough.
Back to the code. It has taken over 1900 lines of code - none of which is likely to be re-used. The code now extracts and reformats all of the old Google Plus posts, links to any relevant photos (where Google actually extracted them), and embed any check-ins or maps. The second stage of the code runs through the extract and plugs the relevant information into the databases. Et Voila... over a thousand new entries have been added to the test version of the private blog - and in 30 minutes time, they should similarly have been added to the production version.
There is some tidying up required where GPlus generated some daft titles or failed to extract the photos - but that can be handled over time.
Sunday, April 07, 2019
Nearly there
It's been a lovely day again today. The Gorse Fox had some football to play this morning so headed out at his usual time. The game was 6-v-5 then 5-v-6 in the second half. It was pretty even in the end, with a final score of 7-6 to the yellow bibs. The Gorse Fox scored his first goal for a couple of weeks having ridden a couple of fairly agricultural tackles and, overall, played pretty well throughout the game.
Back home he returned to the code face. (Did you see what he did there?). The code is coming along well now and as he writes this, he thinks the basic extract and mashup is just about done. What he has realised is that he spent a huge amount of time debugging a problem that he hadn't got. Well, that's not quite true - he has got the problem, but the source of the problem was Google and there's nothing he can do about it. In the extract of Gplus, they have linked to various photos - the problem is that they have failed to download some of the photos so the code points to nothing. There's nothing that can be done, so the Gorse Fox will just have to manually check the few posts affected and add a comment to explain.
One of the features that the Gorse Fox used to use in GPlus was "check-in" where he could drop pin on a map to show where he was. This creates a link to Google maps and this opens up in a new window. The Gorse Fox is considering whether to change this and create an imbedded map instead. He'll sleep on this before deciding, then run a full test run on the test system (tawnyowl).
Just for the record, the Gorse Fox is doing all of this by writing directly to the underlying SQL databases for Wordpress rather than trying to manipulate Wordpress itself. It took quite a while to get an understanding of the data model... but he now has some fairly robust and well-tested code that does this on a daily basis.
Back home he returned to the code face. (Did you see what he did there?). The code is coming along well now and as he writes this, he thinks the basic extract and mashup is just about done. What he has realised is that he spent a huge amount of time debugging a problem that he hadn't got. Well, that's not quite true - he has got the problem, but the source of the problem was Google and there's nothing he can do about it. In the extract of Gplus, they have linked to various photos - the problem is that they have failed to download some of the photos so the code points to nothing. There's nothing that can be done, so the Gorse Fox will just have to manually check the few posts affected and add a comment to explain.
One of the features that the Gorse Fox used to use in GPlus was "check-in" where he could drop pin on a map to show where he was. This creates a link to Google maps and this opens up in a new window. The Gorse Fox is considering whether to change this and create an imbedded map instead. He'll sleep on this before deciding, then run a full test run on the test system (tawnyowl).
Just for the record, the Gorse Fox is doing all of this by writing directly to the underlying SQL databases for Wordpress rather than trying to manipulate Wordpress itself. It took quite a while to get an understanding of the data model... but he now has some fairly robust and well-tested code that does this on a daily basis.
Friday, July 01, 2016
For Posterity
Having spent more hours than seems decent trying to get to the bottom of the problem with internal links in WordPress, the Gorse Fox thought he would document the solution for posterity.
If you wish to use any internal "permalink" style, other than the default, several things have to come together:
If you wish to use any internal "permalink" style, other than the default, several things have to come together:
- Make sure the rewrite module in Apache is enabled (Used for WordPress Permalinks)
sudo a2enmod rewrite - A stanza needs to be added to /etc/apache2/sites-enabled/000-default.conf
# Added by AJM for Wordpress permalink <directory html="" var="" www=""> Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny allow from all </directory>Note that < and > in the text above should be "less than sign" (U+003C) and "greater than sign" (U+003E) but they keep getting interpreted by html as tags and the Gorse Fox can't work out how to avoid this at present - Make sure /var/www/html/.htaccess exists and is writable
sudo touch /etc/www/html/.htaccess
sudo chmod 666 /etc/www/html/.htaccess - Restart apache
- From WordPress Dashboard "Settings" change Permalinks structure to your chosen preference.
Thursday, June 30, 2016
Compost
Thursday - it must be admin. So it was that the morning started with spreadsheets followed by the arrival of the week's shopping, thanks to Ocado. Once we had the basics completed we headed up to the garden centre to get a further planter and some compost.
The rest of the day was spent debugging. The test version of the private blog (on "tawnyowl") works perfectly, but when built on "peregrine", the internal links all fail. At first the Gorse Fox though ht it was something in his code and spent hours pouring over the logic and the database structure. Then it occurred to him to try an empty "site" with just the initial opening posts. This too demonstrated the same problem... it wasn't the Gorse Fox's code after all.
After a lot more checking, the Gorse Fox has decided to rebuild "peregrine" from scratch in case he had created any differences from "tawnyowl". He will use his new configurator with the same configuration scripts used for "tawnyowl". That can wait until tomorrow.
The rest of the day was spent debugging. The test version of the private blog (on "tawnyowl") works perfectly, but when built on "peregrine", the internal links all fail. At first the Gorse Fox though ht it was something in his code and spent hours pouring over the logic and the database structure. Then it occurred to him to try an empty "site" with just the initial opening posts. This too demonstrated the same problem... it wasn't the Gorse Fox's code after all.
After a lot more checking, the Gorse Fox has decided to rebuild "peregrine" from scratch in case he had created any differences from "tawnyowl". He will use his new configurator with the same configuration scripts used for "tawnyowl". That can wait until tomorrow.
Subscribe to:
Posts (Atom)