# Testers for WriteFreely 0.12 Release Candidate **URL:** \ **Category:** WriteFreely\ **Tags:** writefreely\ **Created:** [March 11, 2020, 3:12pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166 "2020-03-11T15:12:11Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![cjeller1592](https://discuss.write.as/user_avatar/discuss.write.as/cjeller1592/32/128_2.png) [@cjeller1592](https://discuss.write.as/u/cjeller1592)\ **Post date:** [March 11, 2020, 3:12pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/1 "2020-03-11T15:12:11Z")
For the upcoming WriteFreely version 0.12 release we are going to put out a release candidate for testing. We’re looking for instance admins who’d want to try it out and give feedback. Let us know if you’re interested! ---
**Author:** ![gytisrepecka](https://discuss.write.as/user_avatar/discuss.write.as/gytisrepecka/32/233_2.png) [@gytisrepecka](https://discuss.write.as/u/gytisrepecka)\ **Post date:** [March 23, 2020, 2:24pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/2 "2020-03-23T14:24:01Z")
Count me in 🤓 ---
**Author:** ![cjeller1592](https://discuss.write.as/user_avatar/discuss.write.as/cjeller1592/32/128_2.png) [@cjeller1592](https://discuss.write.as/u/cjeller1592)\ **Post date:** [March 27, 2020, 6:52pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/3 "2020-03-27T18:52:41Z")
The WriteFreely 0.12 release candidate is now live! Check it out below and let us know what you think: > **[Release v0.12.0rc1 · writeas/writefreely](https://github.com/writeas/writefreely/releases/tag/v0.12.0rc1)** > > g/v0.12.0rc1 ---
**Author:** ![gytisrepecka](https://discuss.write.as/user_avatar/discuss.write.as/gytisrepecka/32/233_2.png) [@gytisrepecka](https://discuss.write.as/u/gytisrepecka)\ **Post date:** [March 28, 2020, 4:14pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/4 "2020-03-28T16:14:48Z")
For me it fails to build on CebtOS 7: ```auto [fedidev@server writefreely]$ make build go-bindata -pkg writefreely -ignore=\\.gitignore -tags="!wflib" schema.sql sqlite.sql go get -tags='sqlite' -d -v ./... go: github.com/writeas/impart@v1.1.1-0.20191230230525-d3c45ced010d: invalid pseudo-version: git fetch --unshallow -f https://github.com/writeas/impart in /home/fedidev/go/src/pkg/mod/cache/vcs/958d5d59e50002212553135624d776253b468040795102a79acec486f36c6922: exit status 128: fatal: git fetch-pack: expected shallow list make: *** [deps] Error 1 ``` I think you haven’t pushed `github.com/writeas/impart v1.1.1-0.20191230230525-d3c45ced010d` version to `github.com/writeas/impart` - latest tag there is still `v1.1.0`. ---
**Author:** ![matt](https://discuss.write.as/user_avatar/discuss.write.as/matt/32/2760_2.png) [@matt](https://discuss.write.as/u/matt)\ **Post date:** [March 28, 2020, 5:21pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/5 "2020-03-28T17:21:10Z")
Hmm, I’m not quite sure… But I did find [this StackOverflow answer](https://stackoverflow.com/a/57366193) about an old version of git that ships with CentOS 7. Maybe that’s the issue? ---
**Author:** ![gytisrepecka](https://discuss.write.as/user_avatar/discuss.write.as/gytisrepecka/32/233_2.png) [@gytisrepecka](https://discuss.write.as/u/gytisrepecka)\ **Post date:** [March 28, 2020, 5:25pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/6 "2020-03-28T17:25:20Z")
Yep, on CentOS 7 I have `git version 1.8.3.1`. But on WriteFreely’s `go.mod` I can see dependency set on `github.com/writeas/impart v1.1.1-0.20191230230525-d3c45ced010d` - is that ok? Because `github.com/writeas/impart` latest version on GitHub is `v1.1.0`. ---
**Author:** ![matt](https://discuss.write.as/user_avatar/discuss.write.as/matt/32/2760_2.png) [@matt](https://discuss.write.as/u/matt)\ **Post date:** [March 28, 2020, 5:29pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/7 "2020-03-28T17:29:32Z")
Yeah, I’m not quite sure how to parse that version number. I _think_ it’s supposed to point to the latest commit on `master`. But to be sure, I’ll push a tag and update `go.mod` in WriteFreely. ---
**Author:** ![matt](https://discuss.write.as/user_avatar/discuss.write.as/matt/32/2760_2.png) [@matt](https://discuss.write.as/u/matt)\ **Post date:** [March 28, 2020, 5:33pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/8 "2020-03-28T17:33:00Z")
Okay, I’ve updated the `develop` branch – give that a shot and let me know if that works. ---
**Author:** ![gytisrepecka](https://discuss.write.as/user_avatar/discuss.write.as/gytisrepecka/32/233_2.png) [@gytisrepecka](https://discuss.write.as/u/gytisrepecka)\ **Post date:** [March 28, 2020, 6:11pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/9 "2020-03-28T18:11:49Z")
Thanks - it builds now (still on git v.1.\*) 🤓 Just built from `develop` branch and installed on [fedi.dev](https://fedi.dev/) 😌 Built on: ```auto CentOS 7 go version go1.13.6 linux/amd64 git version 1.8.3.1 ``` ---
**Author:** ![matt](https://discuss.write.as/user_avatar/discuss.write.as/matt/32/2760_2.png) [@matt](https://discuss.write.as/u/matt)\ **Post date:** [March 28, 2020, 6:18pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/10 "2020-03-28T18:18:01Z")
Awesome!! 🎉 Glad that fixed it. ---
**Author:** ![gytisrepecka](https://discuss.write.as/user_avatar/discuss.write.as/gytisrepecka/32/233_2.png) [@gytisrepecka](https://discuss.write.as/u/gytisrepecka)\ **Post date:** [March 28, 2020, 6:42pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/11 "2020-03-28T18:42:20Z")
I will start exploring 🤓 Already like updated admin dashboard very much 👍 Curious to try out ActivityPub mentions and I’ll try to setup [OAuth with Gitea](https://docs.gitea.io/en-us/oauth2-provider/) as [described in your tutorial](https://discuss.write.as/t/feature-suggestion-login-with-an-account-from-other-websites-e-g-mastodon-github-etc/872/8). ---
**Author:** ![gytisrepecka](https://discuss.write.as/user_avatar/discuss.write.as/gytisrepecka/32/233_2.png) [@gytisrepecka](https://discuss.write.as/u/gytisrepecka)\ **Post date:** [March 30, 2020, 7:41pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/12 "2020-03-30T19:41:09Z")
Is it just for me or ActivityPub mention doesn’t work [on this post](https://fedi.dev/gytis/enable-grub-menu-and-timeout)? 😐 ---
**Author:** ![matt](https://discuss.write.as/user_avatar/discuss.write.as/matt/32/2760_2.png) [@matt](https://discuss.write.as/u/matt)\ **Post date:** [March 30, 2020, 7:53pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/13 "2020-03-30T19:53:07Z")
Hm, clicking the mention seems to work fine… What didn’t work, the notification? Or something else? ---
**Author:** ![gytisrepecka](https://discuss.write.as/user_avatar/discuss.write.as/gytisrepecka/32/233_2.png) [@gytisrepecka](https://discuss.write.as/u/gytisrepecka)\ **Post date:** [March 31, 2020, 8:18am UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/14 "2020-03-31T08:18:58Z")
It seems in post itself fediverse handle (`@gytis@mastodon.lt`) is parsed, but when I try to reply from Mastodon, only blog handle (`@gytis@fedi.dev`) is mentioned 🤔 I have added few more fediverse handles in the post to check mentions. Update: mentions work as expected - problem was because Mastodon cached post which initially was without additional handles to mention. I have created [one more post](https://fedi.dev/gytis/writefreely-activitypub-mentions-testing) and this time it was fine with both Mastodon and WordPress fediverse handles 👍 ---
**Author:** ![matt](https://discuss.write.as/user_avatar/discuss.write.as/matt/32/2760_2.png) [@matt](https://discuss.write.as/u/matt)\ **Post date:** [March 31, 2020, 1:25pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/15 "2020-03-31T13:25:03Z")
Ah, yep. Unfortunately Mastodon doesn’t handle the `Update` activity we send out, so it doesn’t update the post. Glad the new post worked! ---
**Author:** ![gytisrepecka](https://discuss.write.as/user_avatar/discuss.write.as/gytisrepecka/32/233_2.png) [@gytisrepecka](https://discuss.write.as/u/gytisrepecka)\ **Post date:** [April 1, 2020, 2:10pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/16 "2020-04-01T14:10:45Z")
So it wasn’t an issue using git v.1 on server that had sources initialized from earlier, but on blank CentOS server I’ve set up freshly it is **required to have git v.2** - otherwise `go get` doesn’t pull anything. There is quick guide on how to [get git v.2 on CentOS 7](https://computingforgeeks.com/how-to-install-latest-version-of-git-git-2-x-on-centos-7/). I will update my [build WriteFreely from source guide](https://fedi.dev/gytis/build-writefreely-from-source) 🤓 ---
**Author:** ![gytisrepecka](https://discuss.write.as/user_avatar/discuss.write.as/gytisrepecka/32/233_2.png) [@gytisrepecka](https://discuss.write.as/u/gytisrepecka)\ **Post date:** [April 2, 2020, 12:15pm UTC](https://discuss.write.as/t/testers-for-writefreely-0-12-release-candidate/1166/17 "2020-04-02T12:15:59Z")
I’ve also came across some more SELinux denials (this time with static files), but [this guide helped to address them](https://github.com/northbright/Notes/blob/master/nginx/configure-selinux-to-fix-403-forbidden-error-of-nginx-on-centos.md).