Webmastersite.net

Search    Register    Log In   


By on Nov 17, 2018 at 6:32 AM

Thought I'd revive this blog to go into more detail about developments in the WSN 10.3 series so far. Let's start with an entry about the bootstrap-related developments, which have been numerous.

To free things up a bit from the non-bootstrap legacy, WSN now has two different base styles. When using a legacy (non-bootstrap) theme, the schemas/base.css gets called in as before -- but for bootstrap themes, WSN now calls schemas/bootstrapbase.css instead. I've been trimming some legacy cruft out of bootstrapbase.css and trying to let as much of bootstrap's own rules take precedence as possible. This has resulted in some visual mistakes in a few releases, like certain tables not being aligned to top that needed to be because I simplified too much. Hopefully I've caught all of those situations now.

The bootstrap user-editable stylesheet (templates/styles/default.css or templates/styles/bootstrap.css) has changed too. In 10.2 and before, it used an @import rule to pull in bootswatch themes or the generic bootstrap from a CDN. This was problematic if you're sometimes working offline with a localhost installation, and also addde another DNS lookup to a another server that can sometimes slow things down, and increased the chances of downtime since both your server and the theme CDN server had to be working for your site to work right. So what I decided to do was have WSN download and cache the bootswatch themes and display them from the local copy. In order to accomplish that, I had to removed the @import from the style and move the bootstrap loading to the backend code.

You now choose your bootswatch theme or specify a custom bootstrap theme source at Admin -> Themes -> Theme Settings. Instead of displaying the theme from the remote source, WSN downloads and caches a copy of whichever bootswatch theme you select and then displays it from the local copy.
The dark bootswatch styles proved difficult as they normally rely on appending a bunch of rules to the user sty...

Read Full Blog Entry


By on May 27, 2017 at 10:24 AM

Lots of advancements in WSN's mapping functionality lately, as of 10.1.11 Beta 4.

First, the issue of not having all possible pins on the category or search map at once is at last solved. By setting Admin -> Settings -> General -> Map Pins Loading Strategy to "all", WSN will progressively load all applicable pins that are within the current viewport -- and when the viewport changes by drag/zoom, it loads anything needed for the new viewport. It's generally a quick process but there's a loading indicator bar to make it clear when it completes.

Second, I set about making it possible to dynamically filter the map by listing type by checking or unchecking a checkbox for each type. To use this, simply insert {FUNC_ADDFILTERPINSHTML} where you want the checkboxes displayed.

Third, in conjunction with the above I thought it'd be nice to visually distinguish pins of each listing type in different colors. This is now possible by setting the coloredpins tweak. Up to 7 colors are automatically assigned, and a colored pin is displayed by the checkbox to act as a visual key.


By on Apr 19, 2017 at 10:39 PM (Edited Apr 19, 2017 at 10:46 PM)

Adding a couple of new tweaks today: changeswitches and changesettings. These allow you to change the value of any switch or setting using your tweaks.php file, instead of using the admin panel. My personal use case is for my development site where I want to do my testing with reCAPTCHA and alertify turned off, but not actually configure the site that way because my release tools make the development copy's configuration be the default configuration. I'd imagine you might want to use it to create special tweaks files you can upload to a site to put it into a testing configuration, or something like that.

Here's how it works. Open tweaks.php in a text editor. Then add lines like this before the ?>:

$changesettings['stopspam'] = 'bait';
$changeswitches['alertify'] = 0;

Note that switches must always be 0 (turned off) or 1 (turned on). You can add as many settings or switches as you like.

In order to avoid accidentally saving the changed state in the admin, these changes are applied only on front-end pages -- not in the admin panel.


By on Mar 26, 2017 at 6:50 PM

As of WSN 10.1.7, reCAPTCHA will be enabled by default using shared keys with no domain restrictions. This will provide a better out of the box spam-prevention experience on new installations, avoiding the accessibility issues of WSN's internally-generated CAPTCHA.

You may still wish to replace the shared keys with your own keys in order to have control over the challenge level (more human-friendly or more secure against machines).

I've also added a line to the privacy policy page when reCAPTCHA is enabled which explains that it uses cookies and shares data with google, fulfilling EU privacy disclosure law.


By on Nov 15, 2016 at 11:17 AM

Normally, WSN's CAPTCHA option is sufficient to stop spammers from submitting to your site. It can be a bit annoying to the submitter, though, and hard to read at times. It can also be defeated by the more advanced or specifically-targeted bots.

Now you have another option: google's reCAPTCHA. reCAPTCHA has several advantages. First, it can be "solved" with just a click in most cases thus saving the submitter time and effort. Second, when it suspects the user of being a bot, it presents them with problems that are impossible for current AI systems -- such as choosing which of a series of pictures contain a certain thing. Third, the complexity is configurable so you can decide whether to make things easier or more secure.

The drawback of reCAPTCHA is that you have to sign up for keys for each domain name to use it. When you select it from the spam prevention menu at Admin -> Settings -> General, two boxes will immediately appear prompting you for the site key and secret key and there'll be a link above the boxes telling you where to register to get the keys.

reCAPTCHA is available in WSN versions 10.0.32 Beta 3 and later.
<< March 2019 >>
SunMonTueWedThuFriSat
12
3456789
10111213141516
17181920212223
24252627282930
31

Recent Comments