Bug 12137 - start should not be in IPFire Security Hardening Guide paths for new wiki
Summary: start should not be in IPFire Security Hardening Guide paths for new wiki
Status: CLOSED NOTABUG
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: Web Site (show other bugs)
Version: unspecified
Hardware: unspecified Unspecified
: - Unknown - Documentation
Assignee: Michael Tremer
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-12 02:30 UTC by Jon
Modified: 2024-02-05 17:03 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jon 2019-08-12 02:30:59 UTC
Can you move the IPFire Security Hardening Guide (and its related pages) in a path without the "start" directory?

Maybe https://wiki.ipfire.org/optimization/security_hardening

I don't know of a way to move directories...

---

IPFire Security Hardening Guide
https://wiki.ipfire.org/optimization/start/security_hardening


Good Security Practice - Part of the IPFire Security Hardening Guide
https://wiki.ipfire.org/optimization/start/security_hardening/good_security_practice


Additional Security Configuration - Part of the IPFire Security Hardening Guide
https://wiki.ipfire.org/optimization/start/security_hardening/additional_security_configuration


Reducing Attack Surface - Part of the IPFire Security Hardening Guide
https://wiki.ipfire.org/optimization/start/security_hardening/reducing_attack_surface
Comment 1 Michael Tremer 2023-12-15 13:34:43 UTC
Is this still an issue?
Comment 2 Jon 2023-12-18 17:38:50 UTC
yes, but it is fine for now.

I have not found and easy way to move pages from one branch of the tree to another branch of the tree.  Right now I create new and delete old.  And this is far from seamless.

So maybe add this to the "Requested Feature" list as a nice to have.
Comment 3 Michael Tremer 2023-12-20 11:33:22 UTC
(In reply to Jon from comment #2)
> So maybe add this to the "Requested Feature" list as a nice to have.

Yes, we can talk about this... It might not be an every day admin task, but it would be good to keep a proper history of things.

Help me to understand the use case: sometimes it turns out that a page should be elsewhere, so moving should be a one-step operation?

I am not sure how I can represent this in the database then. Should there be a redirect from the old page? Wikipedia has that I believe.
Comment 4 Jon 2023-12-20 17:36:54 UTC
(In reply to Michael Tremer from comment #3)
> Help me to understand the use case: sometimes it turns out that a page
> should be elsewhere, so moving should be a one-step operation?

Yes - one step.  Right now moving text is easy (as expected), but the local Wiki links get fubar'd.  Non-relative and relative links suffer (depending on the distance of the move).  And each needs to be checked and corrected.

There is a note to merge the Optimization section at https://wiki.ipfire.org/optimization) and move items:

"EDITING NOTE: This whole section should go. The pages can all be merged into the pages of the individual add-ons and probably will be found much quicker. FIXME"

So I tried to do that. but it is much tougher than hoped!

One example:
https://wiki.ipfire.org/optimization/traverse_net-to-net_vpn_from_road_warrior

I end up leaving "we've moved" links since there are so many links in so many places (e.g., in the Community). And within the local Wiki page.  Maybe permalink type links would help.

Another "we've moved" example: https://wiki.ipfire.org/optimization/hardware-change

Here is a link not related to the Optimization section:
https://wiki.ipfire.org/addons/mdns-repeater/start

Many of the links that include "start" in the path must be related to on older wiki system.

None of these are the right example since they have none (or little) local Wiki links, but hopefully this helps the Use Case.  I'll keep looking for examples.