[Mkguild] Problems with the archive website

[Alex Green]

Yeah, that's what I was thinking. In that case, it'll probably be easier
just to build the file again from the original than to try to correct the
one already in the database.

-AlexSurikat

On Sun, Jul 19, 2015 at 11:39 AM, Andrew Vineyard <dimensional42 at gmail.com>
wrote:

>  It could also have something to do with how the files were built and
> uploaded. Anyways, there's a nice extension for Firefox that allows you to
> force the browser to display in a specific encoding. The extension is
> called Charset Switcher.
>
> On 7/19/2015 10:26 AM, Alex Green wrote:
>
> Looking around the site and seeing other pages render correctly leads me
> to believe that the problem might just lie in the encoding of that
> particular page in the database.
>
>  The odd thing is, I know at some point that page rendered correctly, as
> I read all the stories up to "Dominion of the Hyacinth" off the archive.
>
>  -AlexSurikat
>
> On Sun, Jul 19, 2015 at 11:21 AM, Andrew Vineyard <dimensional42 at gmail.com
> > wrote:
>
>>  That was going to be my original thought, but when I looked at the files
>> what I saw seemed to match with what I posted. I commented out the line
>> that was having it encode as UTF-8, but it still rendered as that on my
>> Firefox. I think there were a few changes to the browser that affected this
>> too.
>>
>> On 7/19/2015 10:12 AM, Alex Green wrote:
>>
>> To me, it seems the issue is one of character encoding. The browser
>> expects the data to be encoded as UTF-8, but it's actually being sent as
>> iso-8859-1. If you have Firefox, go to view -> character encoding, and
>> select western. The page renders as it's supposed to.
>>
>>  That's not to say that the line breaks shouldn't be there, but they've
>> always been there. Removing them will make most of the diamonds disappear,
>> but there are characters like the apostrophes that still won't render
>> correctly.
>>
>>  I'm not sure what could have changed to cause this. Most likely the
>> configurations for the web server have changed so that now the server is
>> serving pages as UTF-8 where it use to be serving them as iso-8859-1.
>> Although, when I look through the HTML, I see two separate meta tags. The
>> first sets the character set as iso-8859-1, and the second changes it to
>> UTF-8. Removing that second meta tag might fix the issue, but I don't have
>> enough practical experience with HTML to know for sure.
>>
>>  -AlexSurikat
>>
>> On Sun, Jul 19, 2015 at 10:34 AM, Andrew Vineyard <
>> dimensional42 at gmail.com> wrote:
>>
>>>  I've taken a look at the files. Apparently the files were uploaded with
>>> line breaks where there aren't suppose to. That's what is causing the
>>> issues. To give a good example, when I'm looking at the file, I'm seeing
>>> that instead of having everything between the <p> </p> on the same line,
>>> where you see the "?" is where there's a line break in the file. It'll be a
>>> big task to fix it all, do to the complexity.
>>>
>>>
>>> On 7/19/2015 6:25 AM, C. Matthias wrote:
>>>
>>> I have a different issue with the Metamor Keep Archive.
>>>
>>> It appears that a lot of the stories are showing various special
>>> characters as diamonds with "?" inside them.  This is extremely off-putting
>>> and renders stories difficult to read.  I suspect some of them are quote
>>> characters, en-dashes, and so forth.  This is showing up with both FireFox
>>> and Safari.  It is especially bad in my story Inchoate Carillon, Inconstant
>>> Cuckold.
>>>
>>> Somebody definitely ought to take a look into that!  It wasn't at all
>>> like this two weeks ago the last time I checked.
>>>
>>> May He bless you and keep you in His grace and love,
>>>
>>> Charles Matthias
>>>
>>> At 03:13 PM 7/18/2015, Virmir wrote:
>>>
>>> Hello!
>>>
>>> Yes, that was merely a google custom search page.  I'm sure the syntax
>>> has changed throughout the years.  It looks like the service is still
>>> offered, so it's probably just a matter of setting up a new one.
>>> <https://cse.google.com/cse/>https://cse.google.com/cse/
>>>
>>> Regarding the domain, I do own and pay for metamorkeep.com.  This is
>>> no big deal since it is a pittance, however if someone else more active in
>>> the community would like to take up ownership, I certainly wouldn't have
>>> any problem with that (I have like seven of these things anyway).  Whoever
>>> takes it would have to promise to be super attentive and pay the bill on
>>> time to avoid a transform.to situation though.  ;)
>>>
>>> Somewhat related--I actually have the domain pointing to my nameservers
>>> before it goes to Xepher.  This gives us a little more control in case
>>> people have their own sites or blogs and want to use a subdomain or
>>> something. E.g. mishablogsaboutmuffins.metamorkeep.com
>>>
>>>   On Sat, Jul 18, 2015 at 1:42 PM, Alex Green < <alexsurikat at gmail.com>
>>> alexsurikat at gmail.com> wrote:
>>>  The first problem Chris mentioned was a php error. A variable,
>>> Counter, was being accessed before it had been defined. I haven't run into
>>> it, so it looks like whatever caused it has gone away for now.Â
>>>
>>>  The second problem is that the search feature provided by Google has
>>> stopped working. I haven't been able to figure this one out. At first
>>> glance, it appears there is a lot of stuff in the search URL that shouldn't
>>> be there, but even after deleting it and trying to manually rerun it, the
>>> error persists. In that case, the reason it failed might be that the
>>> account that the search feature was tied to has been deleted, but this is
>>> all conjecture as I am totally unfamiliar with how Google's custom search
>>> feature works.Â
>>>
>>>  It might be worth it to ask Virmir about this one as he set it up and
>>> might remember how to do it again.Â
>>>
>>>  P.S. I find it funny that both Chris and my test searches were related
>>> as we both searched for or respective species.Â
>>>  -AlexSurikat
>>>
>>>  On Sat, Jul 18, 2015 at 2:28 PM, Andrew Vineyard <
>>> <dimensional42 at gmail.com>dimensional42 at gmail.com > wrote:
>>>  I'm looking at the site, but I'm not seeing anything wrong with it.
>>> I'm getting access to it and everything. It may have been a slight hiccup
>>> in the server engine. I'll still look into it and see what might be the
>>> problem, but it appears that whatever was happening was simply a connection
>>> error.
>>>
>>>  _______________________________________________
>>>  MKGuild mailing list
>>>  MKGuild at lists.integral.org
>>>  http://lists.integral.org/listinfo/mkguild
>>>
>>>
>>>
>>>  _______________________________________________
>>>  MKGuild mailing list
>>>  MKGuild at lists.integral.org
>>>  http://lists.integral.org/listinfo/mkguild
>>>
>>>
>>>
>>>
>>> --
>>> - Â Virmir | <http://virmir.com>http://virmir.com
>>> _______________________________________________
>>> MKGuild mailing list
>>> MKGuild at lists.integral.org
>>>  http://lists.integral.org/listinfo/mkguild
>>>
>>>
>>>
>>> _______________________________________________
>>> MKGuild mailing listMKGuild at lists.integral.orghttp://lists.integral.org/listinfo/mkguild
>>>
>>>
>>>
>>> _______________________________________________
>>> MKGuild mailing list
>>> MKGuild at lists.integral.org
>>> http://lists.integral.org/listinfo/mkguild
>>>
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.integral.org/archives/mkguild/attachments/20150719/c0307703/attachment.html>