Expected behavior

Functions are tested by an integrated suite.

Actual behavior

Functions are only ever syntax checked.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Make an index and a normal page that sets all possible parameters, and one that has the least possible parameters. Also, one with normal-ish parameters.

• Index
• Page Minimal
• Page Maximum
• Page with Custom CSS/JS

Expected behavior

There should be a CONTRIBUTING.md file within .github.

Actual behavior

There is not.

• Add a CONTRIBUTING.md file.
• Document code styles
• Document security styles
• Document contact points

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Auth info could be one place and billing another.

The header file statically references "elementary". It should not do this, it should likely be the site title.

I'm not entirely sure we want one, since it has a varying length.

• Setting: On Password Change
• Change DB structure to keep old passwords
• Setting: How many / How long to keep old passwords

• Old value-only standard.
• Internal
• Library
• JQL Override
• Async
• Move all to Sitewide['Page']
• Test

    $Page['JS'] = array(
        'normal-script.js',
        'asyn-script.js' => array(
            'async' => true,
        ),
        'jq-library.min.js' => array(
            'library' => true,
        ),
        'internal-script.js' => array(
            'internal' => true,
        ),
        'full-script.js' => array(
            'async' => true,
            'library' => false,
            'internal' => false,
        ),
    );

Expected behavior

There is documentation for hooks.

Actual behavior

There is no documentation for hooks.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Log to database if loaded, otherwise append to log file.

The sitemap, feed, and blog generator all do some special parsing. We should wrap that in a function for everyone to use to extract page variables from within appropriate files.

It's better than just requiring long passwords.

1. https://github.com/dropbox/zxcvbn
2. https://github.com/bjeavons/zxcvbn-php

Sitemaps should paginate after 50,000 links or 10 MB.

10 MB / 50,000 = 200 bytes, which seems about what I am getting now.
Just to be safe, I'm going to recommend paging at 10k.

After 10,000 links, sitemaps should instead be saved into sitemap#.xml files, and a sitemap index created as sitemap.xml

_cron/hourly/sitemap.php
Sitemap Indexes

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
    <sitemap>
        <loc>http://www.example.com/sitemap1.xml</loc>
        <lastmod>2004-10-01T18:23:17+00:00</lastmod>
    </sitemap>
    <sitemap>
        <loc>http://www.example.com/sitemap2.xml</loc>
        <lastmod>2005-01-01</lastmod>
    </sitemap>
</sitemapindex>

The $25 bounty on this issue has been claimed at Bountysource.

Expected behavior

The BountySource badge appears first in the README.md

Actual behavior

The BountySource badge does not appear in the README.md

Blog Indexes should change daily, pages weekly.

Count the / to get a priority. Priorities range from 1 to 0. / should have 1, something like /page should be 0.9, /page/sub-page should be 0.8 and so on down to 0.1.

These should be overridable with $Page['ChangeFreq'] and $Page['Priority'].

The $25 bounty on this issue has been claimed at Bountysource.

• Add setting
• On login

Expected behavior

_templates/schema.php should construct JSON from an array using the PHP function.

Actual behavior

JSON is manually constructed via string concentration.

• Website Logo Schema
• Website Name Schema
• Website Social Schema
• Article Schema

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.