Been doing some work in the Wiki
-
We first have to do some patch work to keep it in working condition for the time being and do the prep work with installing the new software, doing the move, reuploading everything, ...
Once we have the base work done, we'll make a tutorial for editors to do the code clean up, links checking and fixing, pics, everything.
Yup, it might take months till we can call it done. I know the last time we had to do the manual fixes of the TOC and some other code when I last recruited editors and how long that took. And this will be a much bigger project but it needs to be done.
It's not something we did, that we broke, it's been piling up with every update, and it now came to a point where it's time to say goodbye to the tikiwiki.
-
I don't think we need to stop edits just yet, I need to line a lot of ducks up first... when the time comes, I will let you know.
It would however, be very helpful if the edits were planned/prepared before actually doing them on the wiki.
One of the big issues is the massive change logs which takes up 2/3 of the whole Sakwiki DB.
-
@enki_ck said:
We first have to do some patch work to keep it in working condition for the time being and do the prep work with installing the new software, doing the move, reuploading everything, ...Once we have the base work done, we'll make a tutorial for editors to do the code clean up, links checking and fixing, pics, everything.
Yup, it might take months till we can call it done. I know the last time we had to do the manual fixes of the TOC and some other code when I last recruited editors and how long that took. And this will be a much bigger project but it needs to be done.
It's not something we did, that we broke, it's been piling up with every update, and it now came to a point where it's time to say goodbye to the tikiwiki.
Enki, though my coding knowledge is very limited, but given I could understand the new code instruction, I definitely would love to lend my hands to help with the move. Meanwhile, I have planned a few new uploads, but I will wait a little before doing more upload to confuse things further.
-
Yup, using preview instead of save to see how the page looks and how an edit went before saving it is the smart aproach.
But I'd still rather put in man hours into the move and clean up there than crossing the Is and dotting the Ts, formating the pages to make them look better on a platform we will be abandining for a more substanable one in now not so distant future. So people don't waste time for cosmetics that might not be visible in a few months time. If we can keep it for the time being, that's good, but we will need ti prep for the move sooner or later.
-
@comis said:
Enki, though my coding knowledge is very limited, but given I could understand the new code instruction, I definitely would love to lend my hands to help with the move. Meanwhile, I have planned a few new uploads, but I will wait a little before doing more upload to confuse things further.We can do a To do thread to see what people have planned, post pages there in text format, leave pics or catalogs they'd like uploaded, ... So people don't forget or loose the infos and documents they have for the wiki
-
I will help where I can.

-
@Whoey said:
I don't think we need to stop edits just yet, I need to line a lot of ducks up first... when the time comes, I will let you know.It would however, be very helpful if the edits were planned/prepared before actually doing them on the wiki.
One of the big issues is the massive change logs which takes up 2/3 of the whole Sakwiki DB.
Why not start new with the change logs and delete the old once or delete the logs older than a month.
-
I knew it was coming - But I have been dreading this moment :o
Re change logs if we are moving I guess we lose them anyway!
However I have seen that most pages have over 30 versions and some over 75 - And many version logs go right back to the start of the Wiki 10 years or so ago!
And wondered about all that history.If we can keep them I would definitely keep for a year - As someone could make a mistake and it not be found for a long time - Also, at least once, we even had a malicious/spam attack on the Wiki
-
Have limited expertise with this type of effort. I’ve created some HTML pages in the last for my Paintball team, and that’s the extent of my experience, but I’m not afraid to get my hands dirty if you guys need help.
-
Why not cleaning up the change log DB before the change this will make the transition more easy.
-
Just a thought: we should seriously think about the (unwanted) effects of moving to a different wiki system. All links, both internal and external, may or will become invalid. Internal links could probably be fixed manually or maybe automagically with some clever scripting and querying, but external links pointing to SAKwiki pages are a different story. Redirecting old URLs to new URLs (and sending the proper 301 status response) may fix links in search engine result pages, but old links may still exists on external sites for ages.
-
Oh trust me, we're aware of many of the implications a move will have, all things considered, this pretty much covers it:
here's what we're currently using:

what we actually need:

-
Ik, so Huntsman gets the job...
Point taken :(:D
-
Fieldmaster :P
-
@Mechanickal said:
Ik, so Huntsman gets the job...
Point taken :(
:DNot sure I like the way this is going!! :o
-
@Mechanickal said:
Nitpicker! :DVictorinox Nitpicker? Never heard of such a model

-
Nitpicker - Isn't that the model with the Tick Tool

Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login

