redirecting dead wiki links ( linuxsecrets.com/tinycorelinux-wiki/ )

[mocore]

many links around the forum point to [Link deleted, Wiki is fixed.  Rich] which is currently 404

eg http://forum.tinycorelinux.net/index.php/topic,24017.msg151374.html#msg151374


using : https://addons.mozilla.org/en-GB/firefox/addon/redirector/ ( perhaps other similar extensions  exist and could also work ??)

and the below regexp & redirector con-fig

Code: [Select]

Example redirect, try going to [Link deleted, Wiki is fixed.  Rich]
Redirect:^[Link deleted, Wiki is fixed.  Rich]([a-zA-Z0-9_:]*)
to:http://wiki.tinycorelinux.net/doku.php?id=$1
Hint:send old 404 wiki mirror links to the actual wiki
Example:[Link deleted, Wiki is fixed.  Rich] → http://wiki.tinycorelinux.net/doku.php?id=dcore:faq
Applies to: Main window (address bar)



the old broken links will now find new working wiki

hope some find this method useful

i guess similar redirector rule could be a temporary workaround  for the old wiki links mentioned hear: http://forum.tinycorelinux.net/index.php/topic,25957.msg166649.html#msg166649




   

[CentralWare]

many links around the forum point to [Link deleted, Wiki is fixed.  Rich] which is currently 404
eg http://forum.tinycorelinux.net/index.php/topic,24017.msg151374.html#msg151374

@mocore: I just ran a basic search (top right of this page, for example) and came across two posts referring to [Link deleted, Wiki is fixed.  Rich]
(This post will likely now be the third.)
Yes, it's sad when third party sites clean house and things get lost in the wind, but in this case, it might just be easier to update the links in question on the board as opposed to installing firefox extensions (for those who even use FireFox, that is.)

[Rich]

Hi CentralWare
I've already started tracking down the posts with  linuxsecrets  and fixing those links.

[Rich]

Hi CentralWare
Fixed 65 posts that dealt with actual questions and answers.

I couldn't fix this one:
http://forum.tinycorelinux.net/index.php/topic,24278.msg154005.html#msg154005
I get the following error when clicking the Save or Preview button:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@forum.tinycorelinux.net to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Besides this thread, there are 9 other threads containing  [Link deleted, Wiki is fixed.  Rich]  all of
which refer to the Wiki being down. I saw no point in changing them.

[mocore]

@mocore:...
 in this case, it might just be easier to update the links in question on the board as opposed to installing firefox extensions (for those who even use FireFox, that is.)

just ftr ... there is a chrome build of redirector ( afair browser extensions are *now* more or less incompatible format , common api's ect  )
https://chromewebstore.google.com/detail/redirector/ocgpenflpmgnfapjedencafcfakcekcd

while the updates and maintenance (THANKS! * admins / mods ect) are  very much appreciated !! (seasoned greetings btw)
its best not to add to much to the `admin task stack`

with this in mind  redirector  extension puts the regex in the hands of those who browse 

[Rich]

Hi mocore
I tracked the broken linuxsecrets links and replaced them with:
[Link deleted, Wiki is fixed.  Rich]

All except this one:
http://forum.tinycorelinux.net/index.php/topic,24278.msg154005.html#msg154005
Which returns  Internal Server Error  when I try to save (or preview) it.

[mocore]

hi rich
thanks for fixing the links on the forum !

 redirecting via regexp might be *generally* be useful for any non-updated links around in bookmarks on blogs / the internet ect ect

[CentralWare]

All except this one:
http://forum.tinycorelinux.net/index.php/topic,24278.msg154005.html#msg154005
Which returns  Internal Server Error  when I try to save (or preview) it.

@Rich, Remove the dollar signs (x2) where it says $VERSION and it should go through.

Code: [Select]

...
In both files, update the change log to this:
Change-log:     2015/11/22 First version, 7.4.935
Current:        2020/09/23 update 7.4.935 -> $VERSION (matteo)
Replace  $VERSION  with the new version number.
...
Common thread crashes are due to dollar signs and single/double quotes - think of this like escape characters.
MOST of the time, you can remove the offending characters, save the changes, then go back and put them back in afterward.

[Rich]

Hi CentralWare
Thanks, removing the 2 dollar signs worked. I couldn't put
them back, but it didn't change the context in this case so
that's OK.

[CentralWare]

@Rich, yes - that's why I mentioned the "fix" as the reference stayed the same with or without it.  This is mainly pointed out for future reference to EXISTING records (as it's HOPED that all of the upgrades done to SMF have corrected the reason the database records are broken in the first place.)  If you come across an "Internal Error" you're likely looking for escapes from the already-saved-content which are completing a "broken loop."  I'm reasonably certain it's caused by content already in the database record (ie: when you preview or save an update, you're asking SQL to Update THIS to THAT where THIS can be partially unescaped and still get by as PHP can make a few very basic assumptions, but THAT just completely throws the system out of whack) where this record I'm typing right now can have the exact same text and yet survive preview/save since there's no broken THIS content:

In both files, update the change log to this:

Code: [Select]

Change-log:     2015/11/22 First version, 7.4.935
Current:        2020/09/23 update 7.4.935 -> $VERSION (matteo)Replace $VERSION <-- Dollar $ign$ everywhere...

Back in the day (PHPv4'ish I think) we had to url_encode() everything like this if we wanted to save the content "as close to original" as possible yet allow it to be search-able by url_encoding the search string(s) along with it, and though it worked well, it wasn't perfect.  I imagine SMF had similar issues once upon a time and our forum database is "that old" to have lapsed the years (and SMF revisions and PHP versions!)

[Rich]

Hi CentralWare

... where this record I'm typing right now can have the exact same text and yet survive preview/save since there's no broken THIS content: ...

That makes it sound like I should be able to create a fresh
post with the content from:
http://forum.tinycorelinux.net/index.php/topic,24278.msg154005.html#msg154005
with the $ signs added back in and be able to preview it.

I tried that in this thread and still got a forum error.

[CentralWare]

I have the current database downloading as we speak.
When NOT referring to wikis, forums, etc. I'd say you were correct; with content that has a "history" this may not be the case with SMF (I'll know tomorrow when I dissect the DB tables) as it may have logic similar to DokuWiki's (ie: THIS is your first post, after 90 seconds of posting, everything NEW becomes a layer on top of the original instead of replacing the original --- there's a setting for this in Admin but I cannot say to what extent this is carried out.  ADMIN > FORUM > POST SETTINGS > See the last two fields.  How these affect database rows (append/overwrite) I cannot say.)