General TC > Programming & Scripting - Unofficial

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

<< < (2/3) > >>

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:

--- Quote from: mocore on December 03, 2023, 01:04:35 AM ---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.

--- End quote ---

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

--- Code: ---...
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.
...
--- End code ---

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:

--- Quote ---In both files, update the change log to this:

--- Code: ---Change-log:     2015/11/22 First version, 7.4.935
Current:        2020/09/23 update 7.4.935 -> $VERSION (matteo)
--- End code ---
Replace $VERSION <-- Dollar $ign$ everywhere...
--- End quote ---
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!)

Navigation

[0] Message Index

[#] Next page

[*] Previous page