Search    Register    Log In   

By on Jun 11, 2015 at 5:47 PM

By default, the option for visitors to reassign a listing has been showing up for members on both the submit listing and edit listing pages. I feel this can be confusing on the submit listing page and people may end up generating new accounts and assigning listings to them when they don't read carefully. I can't think of any reason by a non-admin would want to reassign a listing during the submission process -- an admin would want to, and a member might want to reassign later when they sell a site but not during submit. So, to limit potential confusion, I'm changing it so that non-admin members only see the reassignment option on the edit listing page -- not on the submit listing page. This change is in the next release of 9.1 and 9.2.

By on Jun 08, 2015 at 8:35 AM

In the last few days: Changed WSN Forum's category names to use <h2> tags for better SEO. Converted the registration defaults to use a serialized array instead of the previous custom format, and added a helper function for changing a registration default. Did a lot of code refactoring for 9.2. Improved the details of parameters in backtraces in bug reports.

Made a lot of progress on the ability for the upgrader to update templates and styles from a theme instead of from the standard. Hopefully this will be finished for 9.2.1. After it's finished I'm hoping to incorporate simple theme selection (with just the best themes shown) into the installer, instead of the guided start. Then at some point I'll try to incorporate bootswatch to let people visually choose the coloring for bootstrap themes.

By on Jun 04, 2015 at 6:42 PM (Edited Jun 04, 2015 at 6:51 PM)

Found a nice tool called browsera for detecting javascript errors and layout problems that are specific to Internet Explorer.

Most of the time, WSN's template conditionals make things easy. There's a long-standing annoying case where they're buggy, though: checking whether a complex HTML field contains a term. Suppose you want to do <IF {LINKDESCRIPTION} contains widget>This listing mentions a widget</IF>. If the description has HTML tags, the conditional can error because the closing tags in the HTML are taken as closing the conditional. Worse yet, if you've enabled search highlighting even simple text can become HTML on the search results page. When someone searches for widget, 'widget' is replaced on the page with <span class="searchhighlight">widget</span> in order to highlight the searched word and this causes the same HTML comparison problem. One workaround for that is to exclude any fields you compare that way from search highlighting, but that's not ideal and it's hard to notice and catch the problem.

In order to have a safer way to do these sorts of comparisons, I'm introducing an optional new syntax {LINKVARCOMPARE[description <,> contains <,> text]}. You'll be able to safely write the conditional as <IF {LINKVARCOMPARE[description <,> contains <,> widget]}>. The first parameter is the template variable name, the second parameter is the operator, the third is the needle. The operators names are the same as in the conditionals syntax: is, is not, contains, does not contain, greater than and less than.

This new syntax will be available soon in both 9.1 and 9.2.

By on Jun 01, 2015 at 8:25 AM

The biggest issue with using a custom theme is that it gets out of date. The bootstrap theme modifies the majority of the templates, so it's especially succeptible to this. I'm thinking about how to allow people to use themes without that drawback. Here's the plan so far. Each theme can include a special file that specifies a URL to get a theme-specific template schema. WSN's manage templates page and upgrade.php can then check that URL, which will return an array of standard uniqueness hashes for theme-customed templates. For templates the user hasn't altered, upgrade.php will automatically replace them with the latest version of that template for that theme. When a user clicks 'revert to standard' in the template editor, the template will revert to the standard for the theme rather than the standard of the default theme. For templates that the theme hasn't altered, the template editor and upgrade utility will use the default theme standard versions so that there are no problems if the last theme update was a few versions back.

I think this plan should significantly improve the experience for people using themes other than the default.

By on Jun 01, 2015 at 6:20 AM

Just released 9.2.0 non-beta, though as the experimental series it's always kind of beta. Most people will probably hold off on upgrading to 9.2 until there's a specific feature you want in it. Note that the 7.1 series is now expired, so the active series are 8.0, 9.0, 9.1 and 9.2. Really there's no reason to use 9.0 though, because the upgrade to 9.1 is easy and 9.1 is now the stable series.

Discovered that the "last post" link for threads in WSN Forum was getting cached to older pages of the thread when using Firefox. This was because I was using an HTTP 301 redirect, I've fixed it to a 302 redirect. In other WSN Forum news, also fixed an issue where forum posts ending in a URL would end up sucking the [/quote] closing tag into the URL link when quoting them.
<< August 2019 >>

Recent Comments