Permalinks change every time the grain is opened #23
Comments
|
Is there any kind of work around possible? E.g. to manually insert in editor some wildcard which will be rewrited in view mode, and manually in editor write path to post "2019/01/name-of-post" next to it. |
|
Hey @searoso, right now its by design that the permalink changes. It is a security feature that each grain gets a random unique i'd when you start up a grain. Even when I was the one who opened the issue back in 2016: I never had a real requirement where I needed these permalinks as the part with the random ID is anyway not what the visitor sees. For example:
As the owner / administrator you choose which format your posts permalinks have. E.g. with year and date or the posts name. The displayed permalink is only an example for that. What your visitor will actually see is anyway depending on your DNS setup and WordPress on Sandstorm can never know what actual base URL you have configured in your DNS. Right now I have two possible ideas to mitigate confusion: From my point of view the benefit of changing something here compared to the effort is super low. What is your opinion? |
|
Thank you for so deep answer!
Use case for this one is management of crosslinks in editor. When I add a link via editor button with integrated search by post name, it inserts link to current grain. (I use hashtagger plugin, which solves similar thing gracefully: generate links in the viewer. But its a wp-plugin.)
Sandstorm-wordpress offers a unique feature: secure by design private WordPress (just don't hit _publish_ button). Private blog plugins seem flawed from different perspectives, and Automatic-hosted option is not private in sense of tracking and data processing. Maybe Sandstorm should sell this point to the public more loudly. (People looking for it: check forums and plugin repository.) In this sense efforts worth it, since internal linking is an important part of journalling.
I like option B) that you proposed; though I feel I understand it not to the bottom.
…On January 9, 2019 9:35:35 AM GMT+03:00, JJ ***@***.***> wrote:
Hey @searoso, right now its by design that the permalink changes. It is
a security feature that each grain gets a random unique i'd when you
start up a grain.
Even when I was the one who opened the issue back in 2016: I never had
a real requirement where I needed these permalinks as the part with the
random ID is anyway not what the visitor sees. For example:
As the owner / administrator you choose which format your posts
permalinks have. E.g. with year and date or the posts name. The
displayed permalink is only an example for that. What your visitor will
actually see is anyway depending on your DNS setup and WordPress on
Sandstorm can never know what actual base URL you have configured in
your DNS.
Right now I have two possible ideas to mitigate confusion:
A) remove the base URL completely from the examples
B) show the unique but permanent URL which is used for DNS
configuration. Here we still have the point, that this is not what the
visitor will see or type in the browser
From my point of view the benefit of changing something here compared
to the effort is super low.
What is your opinion?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#23 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
|
@JamborJan While it would be a somewhat manual step, for heavy WordPress-on-Sandstorm users, wouldn't it be most ideal to allow the user to set the base URL for the permalinks, so it matches what they set up with DNS? |
|
@searoso The big challenge is that because the WordPress package on Sandstorm is geared for web publishing, presumably the goal should be to work well for people web publishing. (Which, mind you, the current configuration doesn't work for either, see previous comment.) I'm curious why WordPress is your ideal "private blog" setup on Sandstorm. Is this content you're keeping solely for yourself, or content you share with other users using the Sandstorm share dialog to grant access to the grain rather than web publishing? I keep a lot of notes and the like on Sandstorm, but I tend towards things like Etherpad or Wekan. I feel like WordPress is a non-ideal choice for private use, so I'm curious what makes it work better for you than other internal document focused options on Sandstorm. |
|
I really love it as knowledge base, and couldn't find anything useful as
replacement. It's too heave and extremely insecure for private
information. But private commercial WP blog does it like a breeze.
I use blog posts, tags, and pages. My posts are mutable informational
chunks that keep some small snapshots of what's going on in my head.
They marked with tags (3-5 usually) covering the contexts for given
information. And page is a wrap-of a tag or two, stitching a context to
be whole. (It's so convenient to create hierarchy when needed.) It
reflects actual state of my world regarding single topic, generalized to
be easy to grasp with a sight of an eye. For details there links to
related posts; the page itself is mostly glued summaries of the posts.
Historical information is easily accessed by clicking the tag.
Going back to post with an idea you like could be fruitful to recover
your state of mind for that moment. And therefore I actually use compare
history feature.
(#39)
I would call Rednotebook the best alternative I saw. But it lacks pages
for wrap-ups and there's nothing for using it with phone. Maybe phone
with Gnome will solve it, but pages would need a fork to maintain.
If you could recommend a system which can capture all of that I would be
grateful. Most of wikis looks very appropriate. But experience is very
different: wiki is just a network of pages not very comfortable for one
person. This belt of posts going down in time appears to be the engine
behind the whole system. That's why I love & hate Confluence. Without
blog feature it would lose so much of dynamic and structure, but
implementation of blog is so disintegrated on the other hand --- there's
even no page to post conversion.
P.s. I also struggling to find a way to easy list posts that have no
tag. It can be done with filters, but it's complex and not available in
phone.
…On 1/9/19 8:26 PM, Jacob Weisz wrote:
@searoso <https://github.com/searoso> The big challenge is that
because the WordPress package on Sandstorm is geared for web
publishing, presumably the goal should be to work well for people web
publishing. (Which, mind you, the current configuration doesn't work
for either, see previous comment.)
I'm curious why WordPress is your ideal "private blog" setup on
Sandstorm. Is this content you're keeping solely for yourself, or
content you share with other users using the Sandstorm share dialog to
grant access to the grain rather than web publishing? I keep a lot of
notes and the like on Sandstorm, but I tend towards things like
Etherpad or Wekan.
I feel like WordPress is a non-ideal choice for private use, so I'm
curious what makes it work better for you than other internal document
focused options on Sandstorm.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGvRyPXpJhRc5ZhTzWRtJPTYmmUsey8ks5vBiZdgaJpZM4Si1UZ>.
|
|
And I remember someone around who use Sandstorm-wordpress in private mode for their team. (They were upset someone clicked publish button, and @xet7 proposed to add unpublish next to it.) |
From @JamborJan on November 28, 2016 15:1
As the name says, permalinks shout stay the same, always.
Current situation
Always after re-opening a grain the permalink will change:
The issue is not as big when you know, that you always can use the main link, displayed on the dashboard.
Desired situation
To avoid confusion of the user, the permalink should always be displayed with the never changing url which is displayed on the dashboard page.
Copied from original issue: dwrensha/wordpress-sandstorm#29
The text was updated successfully, but these errors were encountered: