WHO managed to take the WEB-Site down?

[speedfixer]

It does look like Phat Code.

Next time, I will survey the other sites there and see if I can spot something.

While not perfect, each time I had trouble it did not look like an off-site routing or traffic problem.
(This is what I used to do before I retired ... but it was actually the backbone - higher level transport - that I took care of.)



OK - it happened while trying to post this note.

Does look like something inside that server setup.

I didn't yet get to see how many other sites on the Phat Code list were up to compare.
Without presence or access to the logs, can't tell. Anything more is just speculation.

and again -- it looks like it is our sites problem.

[Imortis]

The Back2BASIC page (also hosted on Phatcode) is doing the same thing. Except no one goes there any more so it doesn't matter terribly.

[caseih]

The problem is with the hosting company, which appears to be webserversystems.com. They also host the back2basic forum you mentioned. Phatcode itself is fine. I tried to go to the webserversystems.com main site, but it's misconfigured. Doesn't do much for confidence in them as a hosting provider! Have the forum admins tried contacting webmaster@webserversystems.com? The problem appears to be in the forum system; static pages seem fine.

[fxm]

In the new wiki (ex wiki2), the note for change is limited to much less characters than previously!
And in addition the number of characters kept is even smaller than that edited on the line!

[fxm]

For the new forum, the better IMHO outweighs the less well.
But for the new wiki, I see only less well (referring also to other faults described above)!

[fxm]

But for the new wiki, I see only less well (referring also to other faults described above)!

2 examples among those catastrophic for tables:
TblVarTypes
OpPrecedence

[Boromir]

Is there any other way to access the Back2Basic website. There are some tutorials on there that have been invaluable. It's hard for me to accept that they are gone forever.

[Imortis]

Is there any other way to access the Back2Basic website. There are some tutorials on there that have been invaluable. It's hard for me to accept that they are gone forever.

Who said anything about "gone forever"? It is just a hosting snafu. Once that is fixed the site should be returned to service.

[Boromir]

ok

[fxm]

For now on the new wiki (ex wiki2), I do nothing to improve the syntaxes which are not or even falsely understood by the new wiki, compared to the old.
This concerns the indentations, line breaks, tables misaligned, and perhaps even other defects.

Can we expect one care for this new sick wiki?

[dkl]

I have updated the wiki again, including its GeSHi plugin. It looks like that fixed the issue where : appeared as \: in the keywords like protected:.

However, the latest Wikka version no longer supports links in the [[url text]] format, and [[url|text]] must be used instead. Because of that I had to do a mass update of all the wiki pages. fbdoc still needs to be adjusted to it, I have half of a patch, that I can probably finish tomorrow.

With regards to code highlighting in the forum, there is CodeBox-Plus for phpBB 3.1, but it seems to be not quite official yet... though I think we can use it again. But its GeSHi (or at least its FreeBASIC highlighting) needs to be updated and should probably be shared with the wiki.

[fxm]

@dkl,

Thank you to work on the wiki problems.

...for example, when editing inside a paragraph, insert a fully blank line (without indentation) does not produce a line break at display, unlike the old wiki. Those already existing with an indentation are well displayed.
One should have to add indentation to each fully blank line inside paragraph!

For each page of documentation, one should completely check the formatting (line breaks, indentation, ...) and correct if necessary.
I think there is no risk in only adding indentations on existing lines (blank or not blank).

For this particular problem, do you think that a solution might be possible at the wiki level itself, or will we have to manually add the correct indentation for each concerned line so that wiki understands that the line break is requested?

If the only solution is to edit manually each concerned page, I can take this work load:
- Checking indentation for line breaks requested but not applied by wiki.

[cha0s]

Hey guys, long time no see eh? I was thinking about FB so I stopped by and saw this. Not good :(

It was most likely this: https://www.drupal.org/SA-CORE-2014-005 exploited automatically by a crawler of some kind. Updating Drupal (and any 3rd party modules) to the latest on 7 branch would be the way to close the hole from being exploited, but I've seen this thing infect other sites and it always embeds code into random places to hide itself. It generally rewrites the 'menu router' in the database so that it can route a certain path to malicious code. If there's any way I can help by getting in there and doing some diagnostics/cleaning, I'll make some time for it.

Anyway I can't tell you how nice it is to see this place still humming along briskly. You guys are awesome.

[fxm]

In the new wiki (ex wiki2), the note for change is limited to much less characters than previously!
And in addition the number of characters kept is even smaller than that edited on the line!

This is really painful when one updates the wiki!
(you never know in advance how many characters will be considered)

[dkl]

Hi cha0s,

it seems you're spot on, I just checked the menu_router table in the Drupal database and it had (I deleted it now) what looks like a malicious entry:

path access_callback access_arguments
cwjvno file_put_contents [BLOB - 201 B]