Before I forget …

Now when you click where it says Click and Read after performing a Newsletter or QA search using Grammar Captive’s custom search engines, your smartphone automatically scrolls to the head of the newsletter. It was a bit of enigma to get it to work, but it greatly improves the user-experience.

Also, if you tab after entering your search phrase, you will go directly to the required number field. The tab functionality of the Reset button has been purposely cancelled, and you no longer have to tab twice to reach the number’s input box.


Imageless Captcha Complete

Grammar Captives modified version of ImagelessCaptcha is now complete. All future keyword searches in Grammar Captive’s custom search engines (see the Local Search menu in the navigation bar on the Grammar Captive mainpage) — will require a Captcha entry before the search can be processed.

Minor dysfunctionality in presentation format remains, but the primary functionality is now well in place. Hooray! Hooray!

Installing Imageless Captcha has been a very involved process that has revealed other problems that need to be address. Recovery from the hardware failure from the summer of last year is still not complete. Obsolete software on an obsolete machine has let to important version incompatibility with the Grammar Captive website.

Because of the complexity of the Grammar Captive site even more problems can be expected in the future. For the moment, the mail function no longer works as it should, and the code must be upgraded. This and the installation of a GIT repository will take priority for the moment.

Have a great week!


GIT Repository

In light of recent suspected hacking and a future need for team development Grammar Captive is taking a pause to set up a GIT Repository with Version Control. The remote depository will be hosted at Atlassian’s BitBucket and the local depository will be set up with cPanel on Grammar Captive’s Lunarpages server.

The short term benefits of this extraordinary change in workflow will be the ability to track all changes to files in Grammar Captive’s development folder.

The long term benefits will be a platform whereby multiple developers can can collaborate on the development of Grammar Captive’s functionality in a secure and shared environment. Think of it as a development chat room with monitored read and write access to the folders and files on the Grammar Captive website.

Up until now the development of Grammar Captive has been pretty much a solo development project with indirect outside support. This has placed the entire burden of development on me — a novice developer who is learning as he goes along.

Preparing for the future.


Dysfunction Resolved

The temporary dysfunction Grammar Captive’s custom search engines has been resolved, and they are now ready for the implementation of Grammar Captive’s, admittedly not unhackable, defense against search engine spam bots.

Related to the above dysfunction was another dysfunction that has also been repaired. Once again, you can discover Grammar Captive’s business model by clicking on Grammar Captive at — the company responsible for Grammar Captive’s current development.


Apology & Next Step

Grammar Captive would like to apologize for the misleading link provided in its last post. Although the link lead to the proper page, the information that the page loaded was incorrect. This problem has been rectified, and you can verify the correction by looking to see that all of the Arab text is aligned right when the link is clicked.

Important progress has been made toward rectifying the problems associated with Grammar Captive’s word clouds. Of the three outstanding problems two have been resolved:

  1. Javascript’s inability to handle Arabic script automatically. (Solved)
  2. Wordcloud2’s inability to handle large amounts of data. (Solved)
  3. The spamming of Grammar Captives custom search engines. (Unsolved)

Although it was initially believed that Grammar Captive was spamming itself through improper use of Matomo, additional research suggests that the spamming originates from a third-party. As soon as the introduction of ImagelessCaptcha is introduced — hopefully by this week’s end, the source of the spamming should become clear.


Two Steps Forward

The stuttering scroll of the GC Tutor insert has been resolved. Apparently, the .animate( ) function is context sensitive and was triggering more functions than were necessary for the achievable task. You can see the correction in action by clicking first on and then again on the phrase And, more … in the text that appears in the main panel of the Grammar Captive mainpage.

In addition, Grammar Captive’s new QR Box has proven to be very handy.

Today, while seated in a café, I asked a young Korean student to scan a copy of Grammar Captive’s QR Box that I had loaded as an item into iBooks on my SmartPhone. It took her directly to the GC Tutor webpage. When the webpage opened, she asked, “English tutor?”. I answered, “Yes” and thanked her for her help.

Without the QR Box things would not have been nearly as magical. Thank you, Chris Barnett, for the suggestion.


One Problem Solved, Two More Added

Have reformatted the GC Tutor panel insert accessed either from the navigation bar of the Grammar Captive mainpage, or from

Although, there is still a problem in the scrolling of the page, a solution does appear around the corner.

The new problems associated with the search engine and word clouds have yet to be resolved. Further exploration is required. They truly are a mystery for the moment.