5015. Continuing the Website Development project, we implemented the automatic creation of 200px-wide thumbnail versions of uploaded images as an adaptation of PHP Thumbnail Generator at Sourceforge. These thumbnails rather than their bigger originals would display on listing pages for speed. We also updated the server with recent user registration, login and Photo Gallery features, realizing in the process that the MySQL on the server used MyISAM rather than InnoDB engine by default and so having to recreate all tables to use InnoDB, for referential integrity support.
5041. Website Development: Decided to disable the Submit button on the Add Photo form until the photo image file was specified. Began setting up the structure of the Services page.
5052. Website Development: Continued implementation of the Services page, in such a way that an admin user could change the photos displayed there at any time, introducing new categories for photos along with the first triggers for the database.
5074. Website Development: Began preparing for the implementation of the eShop page and the (admin-only) products maintenance to go with it, checking out the structure of our Online Shop, the existing eShop page of the old Greek site and finally studying the pictures displayed on that old page so we could transfer them to the new site.
5085. Website Development: Studied and programmatically extracted all but 12 of the images from the old site’s eShop page for use in our own eShop implementation.
5096. Website Development: Copied and imported the remaining 12 images from the old eShop page then moved on to product maintenance, getting the product index listing done, with actual editing form coming up next.
5100. Website Development: Worked on the product listing, deciding for it to also serve as the new eShop page. Coded for selected areas like the draft product editor form, changing currency and recalculating prices based on selected currency. When the old eShop images are uploaded to the server they—from being automatically assigned higher sequential photo IDs—would push the over 40 recently uploaded and newer images down on the Photo Gallery and as the client would probably not like this we’d been thinking we might need to reload the photo data afterwards, after manually editing it. Today we arrived at a better solution, drafting a database procedure to swap ranges of IDs of the images, testing it successfully.
5133. On the Website Development project, we corrected an issue noticed with search of the product list, updated the dictionary with Greek terms for expressions used on the eShop and product maintenance pages, created a script to assign the 2016 image dates to all the eShop products for their date-added values, rather than using current 2020 dates, more ideal since they weren’t new images, and finally began work on showing home page banner images below the slider. We received two emails from the client in response to the new Labelwriter candidate listing update implemented last month, suggesting an alternative, slightly different report presentation format.
5144. Website Development: Finalized the first version of the website with the display of three banners on the home page below the slider, did some general testing and review and finally started updating the server.
5155. Website Development: Completed updating the server, discovering in the process a minor fault in our photo ID swapping code: When handling a range of IDs the very last one was ignored. This would be easy to fix, by changing >= in a line of code to just >.
5181. Following the review of validity of data entry done by users of the Cooperative Society module of FrontAccounting in February, the need for training of the new users was established. As a result of the present coronavirus pandemic the consulting client for them now suggested an “online” form of remote training, and we considered how this could be done.
5192. Website Development: We implemented a couple of minor adjustments to the website, suspending the saving of language and currency changes in a global database table and correcting the issue with the photo id swapping procedure. We checked to see what would happen on attempt to delete a record that was referenced elsewhere (a database error would be issued) and began work on implementing the extra feature of exchange rates maintenance.
5192. When we wanted to process new purchase order items in MoneyBooks Accounts Payable, a couple of errors resulted involving the absence of the unit value in generated Inventory records; the SQL code that handled the processing was revised to address one of the issues.
5203. On the Website Development project, following a report by the client of inability to submit product name and price changes we investigated accessing the site from an Android phone, going through product editing and photo upload and noting how these might be challenging for the user. Later we corrected the second unit value issue during posting of a receipt MoneyBooks Inventory transaction after realizing why it was happening, the GL link setting being off for the particular transaction. Back to the website, we worked on the exchange rate editor implementation, finalizing on the data display and using the same button for both editing and submission, now left to actually submit the new exchange rate entered to the database via an Ajax call.
5214. Website Development: Set up and debugged the Ajax call and database updating code for the exchange rate table, getting over the puzzling situation of the exchange rate value sent to the database having “undefined” attached to it, for example 418.8110undefined.
5225. Website Development: Finalized the exchange rate button behavior on the site. Investigated client’s issue with product form submission, examining audit trail records and concluding that the user didn’t enter a product name or more likely entered a non-numeric value for photo ID, the two instances when the Submit button would not work. We updated the server with the exchange rate maintenance feature and finally turned attention to submitting the new site to search engines via entireweb.com, and later Microsoft’s Bing Webmasters.
5236. Began looking into screen recording (screencast) solutions, downloading Screencast-O-Matic with the option of creating free screen recordings, finding out after install that it still needed internet access to work.
5240. We did a search for screen recorders at Sourceforge, downloaded and installed CamStudio and began going through it. For the Website Development project the puzzling issue the client reported about inability to submit the product form after editing was resolved after—on seeing a photograph of their phone’s screen following the submit attempt, which was presented via Facebook—we realized the issue was actually due to an error about a missing database user function, so resolving it was easy.
5251. Website Development: Backed up the server database, redefined the product foreign key specification so referenced photos in products could be deleted and finally removed three photo records inserted by the client that had no photo files, one of which the client couldn’t delete earlier (due to referential integrity restriction).
5262. Website Development: Strengthened the Photo Gallery add and delete functions so that no photo record got stored without a photo image file, set the CodeIgniter environment for the application to “production” rather than “development” on the server to minimize appearance of error message screens; ensured image files existed before trying to delete them, adjusted the failed user login message and set name and email defaults on the contact message form when a user was already logged in.
5284. Website Development: Began implementing audit trail maintenance based on code from LVReg. Started on video recordings with CamStudio to demonstrate adding photos to the Photo Gallery, first without and then with sound.
5295. Website Development: We carried out a second adding-products video recording to improve on the first. The .avi file produced by CamStudio of 1.6 GB size (3 minutes 28 seconds duration) was titled and edited with Windows Live Movie Maker, that saved to a 10.7 MB .wmv file in 7 minutes. This was converted to .mp4 format of size 11.3 MB (3 minutes 23 seconds duration) with VLC Player and we tried it out on different desktop players and the Windows and Android mobile smartphones, finally uploading to the client’s server and informing the client.