Ah, yes. Our goal here was to make the current theme responsive rather than create a whole new template. The sites volunteers (e.g. staff) don't have the time to create a new template from scratch, nor do we have the desire to. The site was functional prior and it still is, despite all the remarks on how bad it is. At the heart, it's the same style as the old site but with a few cosmetic tweaks. Maybe in 5 or 7 years we'll revisit and actually create a new template. Cemetech6 was released in 2008 - 7 years ago - after 2 years of development. We did this version, dubbed 6.5, in about 3 months. 5 months tops. I think it's safe to say the style has tested the age of time and has held up remarkably well. It's not like Cemetech still looks like a Geocities community, so I think we'll be good for 7+ more.

There was certainly discussion about whether we should start from the ground up versus adjusting the current template before we started.
comicIDIOT wrote:
Ah, yes. Our goal here was to make the current theme responsive rather than create a whole new template. The sites volunteers (e.g. staff) don't have the time to create a new template from scratch, nor do we have the desire to. The site was functional prior and it still is, despite all the remarks on how bad it is. At the heart, it's the same style as the old site but with a few cosmetic tweaks. Maybe in 5 or 7 years we'll revisit and actually create a new template. Cemetech6 was released in 2008 - 7 years ago - after 2 years of development. We did this version, dubbed 6.5, in about 3 months. 5 months tops. I think it's safe to say the style has tested the age of time and has held up remarkably well. It's not like Cemetech still looks like a Geocities community, so I think we'll be good for 7+ more.

There was certainly discussion about whether we should start from the ground up versus adjusting the current template before we started.


Don't get me wrong, I have had no issue with the theme/design in the past, I just thought we were taking open suggestions. I know it takes forever to upgrade because my city has had the same website for 15+ years. We are just now getting around to making it modern and up to date. Honestly, I haven't seen any real Wiki/Forum Design I like more so then the current classic design that Cemetech and others use so until then, I'm not complaining.
I have been receiving a sax chat error since the upgrade as pictured below:



Win7 64-bit SP1
Chrome Version 45.0.2454.85 m
IE11 Version 11.0.9600.17914

It may just be my work firewall - but it was working fine before the upgrade.

EDIT - Here is what the console is saying:


Code:
Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED
saxjax.js:58 ERROR: request id 1.1 error 0 happened
saxjax.js:58 WARN: request errored, status: 0, number of errors: 1
https://cemetech.net:5280/http-bind Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED
saxjax.js:58 ERROR: request id 2.2 error 0 happened
saxjax.js:58 WARN: request errored, status: 0, number of errors: 2
https://cemetech.net:5280/http-bind Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED
saxjax.js:58 ERROR: request id 3.3 error 0 happened
saxjax.js:58 WARN: request errored, status: 0, number of errors: 3
https://cemetech.net:5280/http-bind Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED
saxjax.js:58 ERROR: request id 4.4 error 0 happened
saxjax.js:58 WARN: request errored, status: 0, number of errors: 4
SAX.setLogLevel(0); SAX.connect();
saxjax.js?5:58 DEBUG: Got credentials 1961,6ce1e6ce8e59faf7082ed454c15a6f73
saxjax.js?5:58 DEBUG: _throttledRequestHandler called with 1 requests
saxjax.js?5:58 DEBUG: request id 6.0 posting
saxjax.js?5:58 DEBUG: request id 6.0 state changed to 1
undefined
strophe.min.js:3 OPTIONS https://cemetech.net:5280/http-bind net::ERR_TUNNEL_CONNECTION_FAILEDl @ strophe.min.js:3a.Bosh._processRequest @ strophe.min.js:3a.Bosh._throttledRequestHandler @ strophe.min.js:3a.Bosh._connect @ strophe.min.js:3h.Connection.connect @ strophe.min.js:2room.connect @ saxjax.js?5:473(anonymous function) @ VM81:2InjectedScript._evaluateOn @ VM70:904InjectedScript._evaluateAndWrap @ VM70:837InjectedScript.evaluate @ VM70:693
saxjax.js?5:58 DEBUG: request id 6.1 state changed to 4
saxjax.js?5:58 ERROR: request id 6.1 error 0 happened
saxjax.js?5:58 WARN: request errored, status: 0, number of errors: 1
saxjax.js?5:58 DEBUG: _throttledRequestHandler called with 1 requests
saxjax.js?5:58 DEBUG: request id 7.1 posting
saxjax.js?5:58 DEBUG: request id 7.1 state changed to 1
strophe.min.js:3 OPTIONS https://cemetech.net:5280/http-bind net::ERR_TUNNEL_CONNECTION_FAILEDl @ strophe.min.js:3a.Bosh._processRequest @ strophe.min.js:3a.Bosh._throttledRequestHandler @ strophe.min.js:3a.Bosh._onRequestStateChange @ strophe.min.js:3
saxjax.js?5:58 DEBUG: request id 7.2 state changed to 4
saxjax.js?5:58 ERROR: request id 7.2 error 0 happened
saxjax.js?5:58 WARN: request errored, status: 0, number of errors: 2
saxjax.js?5:58 DEBUG: _throttledRequestHandler called with 1 requests
saxjax.js?5:58 DEBUG: request id 8.2 posting
saxjax.js?5:58 DEBUG: request id 8.2 state changed to 1
strophe.min.js:3 OPTIONS https://cemetech.net:5280/http-bind net::ERR_TUNNEL_CONNECTION_FAILEDl @ strophe.min.js:3
saxjax.js?5:58 DEBUG: request id 8.3 state changed to 4
saxjax.js?5:58 ERROR: request id 8.3 error 0 happened
saxjax.js?5:58 WARN: request errored, status: 0, number of errors: 3
saxjax.js?5:58 DEBUG: _throttledRequestHandler called with 1 requests
saxjax.js?5:58 DEBUG: request id 9.3 posting
saxjax.js?5:58 DEBUG: request id 9.3 state changed to 1
KermMartian wrote:
To be more specific, I have been the one championing those thin boundaries, as they were . However, I'm more than happy to bow to public opinion if I'm the only one who actually likes them. I'm resistant to making every maroon box border curved, but I'm willing to let the white boundaries go away if absolutely no one likes them (and I'm heavily weighting the opinion of the staff on this one over users).

M. I. Wright: I agree about all of those being too close, thanks. As I was discussing with Runer, that jumpbox may be removed entirely.
Meh, I am unsure if I like the lack of lines:



I could live without them if they were removed, though.
tr1p1ea wrote:
I have been receiving a sax chat error since the upgrade as pictured below:

...

It may just be my work firewall - but it was working fine before the upgrade.
Looks like a firewall, yeah. I've adjusted SAX to proxy through the main web server, so it should work for you now. This may also help the certificate issues OSX users were seeing (since they're now talking to the actual web server).
Chat is working now Tari, nice one Smile.
A little annoying: The quick reply messag box is to high on my small kindle its width is fine, but its heighth is a bit to much. (it makss it look fat) Razz

EDIT: The profile page is also a little messed up on mobile. You have to use the sideways scroll bar to see th links to files, an when using it,the border doesn't follow. Maybe you guys could remove the scroll bar? (please not that I am on my kindle paperwhite, so the problem may just be on my device only.

EDIT2: The sax popout does not create a clickable link for edits and osts, and I assume topic creations for topics with names like this: "topic title [codetype]" It happened with lazer, and shades. All other posts have been clickable. I believe that the brackets mess it up.

EDIT3: The PM inbox is slightly messsed up, with lines through the storage usage and between messages. Again, this may be because of my kindle, and I can deal with it.

Oh, and could we get an option to go back to 6, if we don't like the mobile setup? (mainly the absence of sax wherever i go.)
Styling bug: Profile page's post frequency graph is awkwardly squished. Chrome 45.0.2454.85
Just a reminder that I'm aware of the problems with the profile page (see the Known Bugs/To Do list earlier in this thread, replicated again below); I'll deal with it soon. I've also adjusted how the markdown links are generated to make more IRC clients happy about making the links clickable.

Known Issues/To Do
  • New post/new topic buttons are not consistent height
  • Images stretch out the topic review on the posting page. It needs to be switched away from a table to a modern layout
  • SAX remains active when hidden/page unfocused
  • SAX highlights you if you speak on IRC
  • Weird search tool layout on older Chromes
  • User profiles need to be made responsive and fixed up
  • Memberlist needs to be made responsive
  • UTI viewforum/viewtopic/index pages need to be ported to the new styles
Sorry, I just feel that the new design has gotten a lot of whiplash. Overall, I don't mind it, and just wanted to say thank you for continuing to maintain this site and providing helpful feedback! Smile
Private messages don't seem to have a reply button. Chrome 45.0.2454.85
I have a reply button on Chrome and Safari; are you able to dig into the source using the inspector and relay us relevant information?

Strangely enough, I've got a bug. When highlighted with a link in the message on SAX, the link has light gray text with darker gray background. It seems the ".saxhighlight a" property has a background color of "#bbb" while the text color is "#eee" for ".sax-message a." All while ".saxhighlight" has a background color of "#000." It seems .saxhighlight is getting two background-color properties, one for the div and one for the link since the link is the only text wrapped in an <a> tag.




Code:
<li class="sax-message saxhighlight"><span class="sax-timestamp">1:02:19 PM PDT</span> <span class="sax-username" title="cemetech@cemetech.net/1993072281143393334869107">[Cemetech]</span> comicIDIOT added a post in [<a href="http://cemete.ch/p239498">Cemetech 6.5 Bug Reports</a>]</li>
Unicorn wrote:

EDIT2: The sax popout does not create a clickable link for edits and osts, and I assume topic creations for topics with names like this: "topic title [codetype]" It happened with lazer, and shades. All other posts have been clickable. I believe that the brackets mess it up.


Here's a screenshot of it happening on regular SAX

Can you supply us with relevant information (if you need a refresher, the first post of this topic has some guidelines). That'd help a lot. Good Idea
comicIDIOT wrote:
Can you supply us with relevant information (if you need a refresher, the first post of this topic has some guidelines). That'd help a lot. Good Idea
He's just saying that square braces in the link title make the regex fail, and he's right.
Oh, I see the issue regarding that now. Also, another bug report:

When checking up on the Reply Button in PM report above, I noticed the second reply button is super small.



The table cell this image sits inside of has a attribute of colspan="3" while the lower image one does not have this attribute.


Code:
<td align="left" valign="middle" colspan="3"><a href="privmsg.php?mode=reply&amp;p=21040"><img src="/forum/templates/Cemetech6/images/lang_english/reply.gif" alt="Reply to message" border="0"></a></td>

<td><a href="privmsg.php?mode=reply&amp;p=21040"><img src="/forum/templates/Cemetech6/images/lang_english/reply.gif" alt="Reply to message" border="0"></a></td>
(SAX) - The underlining for links is a bit messed up on different zoom settings. Above 125% zoom it is perfectly fine, but at 110% or lower, if the link is too long, it won't underline the whole link, as seen in the following pictures. Chrome 41.0.2272.118.

(Look at SAX in the left)



KermMartian wrote:


Known Issues/To Do

  • SAX highlights you if you speak on IRC

Or post/login/whatever.
Michael2_3B wrote:
(SAX) - The underlining for links is a bit messed up on different zoom settings. Above 125% zoom it is perfectly fine, but at 110% or lower, if the link is too long, it won't underline the whole link, as seen in the following pictures. Chrome 41.0.2272.118.
That's all CSS. I'd be extremely surprised if we somehow made your browser screw up CSS.
Tari wrote:
Michael2_3B wrote:
(SAX) - The underlining for links is a bit messed up on different zoom settings. Above 125% zoom it is perfectly fine, but at 110% or lower, if the link is too long, it won't underline the whole link, as seen in the following pictures. Chrome 41.0.2272.118.
That's all CSS. I'd be extremely surprised if we somehow made your browser screw up CSS.


That's actually from a bug that comic mentioned above, there's a black border on the links, which overlaps the underline.
  
Page 3 of 6
» All times are UTC - 5 Hours
 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

 

Advertisement