As someone who has used your write.as API, python 2 glitch code to search my write.as blogs, I’d like to mention, and thank you for, the following two things that I did not know how to do and these are made perfectly clear in this new code:
Although I could understand and follow the write.as API code, it was not clear to me how to do WriteFreely API code and I was not able to find documentation on it. This writefreely code you made for bix completely cleared that up. As an example, the following excerpt from search.py:
def getAll(alias):
c = writefreely.client('<enter a writefreely instance name>')
And including in .requirements.txt => writefreelyapi
Your new code for bix is python 3, which is a great example of how to write glitch apps in python 3. You had previously given us some python 3 glitch code for other apps, but this now provides the way to upgrade any earlier write.as or writefreely API search code to python 3.
You are welcome @bugbuster! Glad you found the documentation.
And you got it - the WriteFreely and Write.as API code differ in how you instantiate the client. Since the API endpoints are similar, just about everything else is the same.
Here is a boiler plate WriteFreely search app (it has @OddBloke’s blog in there as a test). The code and documentation is a bit more laid out so feel free to remix it for your own use.
Yep! I created a remixable version of the app here. It has my blog set up with it if you’d like to test the functionality.
@bix, the results from your blog will look different because you don’t use titles. So what I did was make a custom test version of the app here that includes your CSS and creates a 'date-preview ’ format of the search results. Feel free to remix/look at the code here.
Hm. I was trying to make it easier to use my custom CSS in this sort of thing by putting it in a github repository, but testing it on a WF blog it won’t at-import, even though I have Google fonts loaded via at-import.
Github repos are weird in that they technically do not host your CSS as a static file. This means you are unable to at-import them. However, you can enable Github pages which allows you to host the raw static file, allowing you to at-import them.
What you do is go into the settings of your repo and scroll down to Github Pages. From there make the ‘Source’ your master branch. It should then inform you that your project is now published at a Github Pages url that looks like https://bixgit.github.io/bixblog/.
Now add the file to the route so it looks like: https://bixgit.github.io/bixblog/bixblog.css. Then you should be able to at-import it.
But besides that, does the search functionality in the app work for your use case?
Doh, I totally overlooked that @bix. Perhaps it is there for easier copy and pasting? I don’t know why the “raw” link doesn’t work. Might be a security measure beyond my understanding.
But I tested at-importing a CSS file from a Github pages link and it worked for me. Let me know if it does the trick for you!
Yes, getting the link into the navbar requires Custom JS. But if you go into Customize and change your Preferred URL to bix.writeas.com, you then can use Custom JS for your blog.
While you wait for your domain (or when you have it), add this to the Custom JS, putting in the placeholder Write.as post url and the search app’s url:
var a = document.querySelector('a[href="https://bix.writeas.com/search"]');
if (a) {
a.setAttribute('href', 'https://bix-search.glitch.me/');
}
I would look into the developer docs, specifically what values are returned when you retrieve a post. That is what I reference in the code to return posts that match a search result.
Of note: should WF/W.a ever get native search, please don’t do it like this Glitch kludge where you can’t link to search results. Linking to search results is a must-have.