I’ve been working on a patch for WordPress that involves fixing the incorrectly stored timestamp stored as part of WordPress image metadata. I already do something like this in my Simple Location plugin, but I’ve found a way that works more simply. To summarize the issue, there are multiple date...
I hacked together some tweaks to add the following:
- Improved support in my theme for time related microformats including
- Because I post so frequently, I added a visible timestamp next to the date so it’s easier to follow my timeline of posts.
- I removed the data for my location, weather, and syndication links from
the_bodyof my posts and appended it to my post meta data. This should prevent it from showing up in Webmentions to others’ websites or in syndicated copies, but still be available to parsers to attach that data to my posts in readers and other services.
- I modified my CSS so that the text in the Simple Location and Syndication Links plugins matches that of the rest in its section.
- I added a cute little bullhorn icon in front of my Syndication Links so that it has some parallelism with the rest of the meta data on my site.
- I’d always liked the idea of adding in related posts data on my site, but didn’t like how it had worked in the past. Things were even worse with replying to other people’s posts as my markup (and far too many others I’ve seen in the WordPress world) was hacky and caused the related posts data to show up in their Webmentions sent to other sites. I looked through some of Jetpack’s documentation and figured out how to remove their Related Posts functionality from
the_body, where it defaults, and append it instead to the post meta section of my posts. It’s not perfect yet, but it’s much closer to how I’d like it. Best of all, that data shouldn’t show up in my replies to other sites now either! I had disabled the functionality ages ago because it made me feel like a rude-IndieWebber.
With IndieWebCamp Online 2020 coming up this weekend, I hope to fix a few outstanding issues and roll these changes up into my open sourced IndieWeb Twenty Fifteen WordPress theme as my hackday project. If you’re using it on your own site, do let me know. Not that I can promise to fix it if it’s broken in places, but I’d at least like to know how it’s working out for you or where it could be improved.
Things left over to fix:
- Simple Location data still needs some CSS help to display the way I want it to.
- I need to target the Simple Location icon so I can have its color match that of the other icons.
- Because so many of my posts don’t have titles, I’ll need to tweak something there so that the Jetpack related posts will pick up better meta data as a pseudo-title instead of displaying the relatively context-less commentary that appears in
- It may take a day or two for the related posts to populate properly, but I should make sure that it’s putting out relevant/interesting results.
- Is it worth adding a default featured photo for the related posts that don’t have one? Could I pull one from other meta fields for some classes of posts?
For any of the date archive pages on my site you can add
/map/ and get an archive of all the places I’ve made posts on my website with location data for that time period, so for example:
/map/to date-based archives and using Google maps as the map provider, the map doesn’t display on the page.
Released some minor bugfix editions today.
- Rounds all numbers to a maximum of two decimal points, as I introduced a bug in the last version that would fail to fill in numbers in the post editor due form validation requirements.
- Extracts additional location information from Compass…mostly the information I store when I’m on a plane, to generate a better description of the location. It also passes this info to WordPress more effectively so it could do more in future.
- I also introduced a new location provider. If set, if you enter a 3 letter airport code in the location name box, it will replace it with the location and name of that airport, as well as the weather. In future, I may add a similar reverse address lookup for people.
- Misc bug fixes
- Some bug fixes introduced in 4.2.0
- Due to the request to allow syndication provider checkboxes to be checked by default, I introduced two new filters: syndication_link_checked and syndication_link_disabled. The first parameter of each is a boolean that if true, will set either checked or disabled on that Syndication Provider. The second and third parameter is the uid of the provider and the post_id of the post.
On my recent trip, I took Southwest Airlines for the first time in many years. At Indiewebcamp New Haven, I set up Aaron Parecki’s compass project to send my location data to. I have 59MB of location data since March 3oth, 2019. The problem is transforming the input from Southwest into the format ...
Version 3.6.3 of Simple Location has been released. This adds Aaron Parecki’s Compass server as a location provider. Location providers in Simple Location look up the current location of the user. As I write this, I realize that I set it up to globally look up the location, and I could make it, ...
One of the features in Simple Location that doesn’t get much notice is the Last Seen functionality. Simple Location adds a section to your WordPress user profile called Last Reported Location. It allows you to set the last reported location for a given user. It reports latitude, longitude, altit...
As an update to the release I did earlier this week, I’ve released version 3.5.2 of Simple Location for WordPress. It fixes a long standing visibility issue, fixes widget titles which were introduced in 3.5, and adds a variety of style changes provided by a third party submitter(Thanks Asuh.com). ...
Perhaps it’s related to the recent fix that was causing private posts to be marked public?
Version 3.5.0 of my location plugin, Simple Location, is now out(forgot to push a fix and had to release 3.5.1 as well). Simple Location is, as time goes on, anything but Simple. It is all about location, including the weather at your location. It adds this to posts, and offers several simple widget...
Simple location’s privacy setting seems to override the post’s public/private settings on my site as well. Perhaps it’s a naming conflict (function/filter/etc.) with WP’s core content visibility code?
In any case, I can’t make a post private while Simple Location is installed/activated either. This seems to happen regardless of other plugins. I do seem to be able to use @vishae’s method of using the quick edit option to change a post to private. I’m not sure if this may indicate a potential solution to the issue based on what is firing on a post save/update versus what fires on a quick edit save.
Additionally, I don’t seem to be able to mark a particular location as “private” in a post either as upon saving it it defaults back to public in the UI. I only seem to be able to use “public” or “protected” options for locations.
I kind of like the Satellite map views, particularly for the Ireland stops. May be useful to have a toggle per post to do that versus street map view for more city-based posts.
I don’t do it often, but checkins on hikes or vacations would be cooler with satellite view (or topographic view if they had it) while city-stops would be better displayed with traditional line maps.