The essential news about content management systems and mobile technology. Powered by Perfect Publisher and XT Search for Algolia.
The News Site publishes posts to the following channels: Facebook, Instagram, Twitter, Telegram, Web Push, Tumblr, and Blogger.
Phoca Panorama[1] version 3.0.0 stable has been released. This version is designed for Joomla! 3.2.
Documentation: Phoca Panorama documentation[2] site
Download: Phoca Panorama download[3] site
Demo (video): Phoca Panorama demo[4] site
Whole frontend component parts are styled by Bootstrap 3 (if you template uses Bootstrap 3, just disable loading of Bootstrap CSS and Javascript in Options, if your template uses Bootstrap 2, you should test to enable/disable loading of Bootstrap 3, it can be in conflict with Bootstrap 2).
If you have tested Beta version and you will upgrade to stable, you need to upgrade sql table manually:
ALTER TABLE `#__phocapanorama_items` ADD COLUMN `iframe_link` text;
Please read documentation[5] before testing this component.
If you find any bug, please report it in Phoca Forum[6]. Thank you.
Read more https://www.phoca.cz/news/768-phoca-panorama-3-0-0-released
Here is new version of amazing Joomla membership extension - Emerald 9.135.
This release we added Kunena[1](com_kunena) forum rule adapter. This adapter makes it easier to assign rules and allows better restriction control. You may select categories to protect topics view access or topics submission or replay.
This is perfect if you want to include to your plan access to some VIP forum categories for paid customers. Thus you always sure that one who posted there, is a paid customer and should be served with priority.
And one little feature. You may allow users to see list of the topics but restrict full topic view, or you can restrict list topics view as well.
It is worth to mention that Emerald could restrict Kunena topics view, submission or replay even without this adapter. Emerald's free universal rule adapter would allow to do that too.
Affected files
Read more https://www.mintjoomla.com/blog/item/330-update-emerald-v-9-135-stable.html
Read more https://feeds.joomla.org/~r/JoomlaExtensionsUpdated/~3/Ca9r75ZBJIA/5615
The Joomla! Extensions Directory Team is please to announce that the Terms of Service has been updated and will take effect February 1, 2014.
4.1.d We will be removing Translations and Tools that do not use the Joomla installer (excluding extension specific extensions).
4.1.e We've integrated the JED Submission Checklists.
4.4 We have changed the distribution models from "Commercial" and "Non-Commercial" to "Free" and "Paid".
Changing distribution models in either direction will result in the loss of reviews/votes.
Extensions that require any form of payment, trade or connect to a commercial service that requires a payment to function will need to be listed as "Paid".
8 We're adding a Dispute Resolution process, which will be completed by the end of Q1 2014.
13 Future ToS updates will be announced 30 days prior to implementing changes.
Other We've removed the requirement of using specific text when requesting reviews.
To see how this change applies to you be sure to read the entire Terms of Service. You can comment and ask questions about these changes in this forum thread.
Read more https://community.joomla.org/blogs/leadership/1793-the-jed-terms-of-service-updated.html
Express has a few helper methods that support configuration. There are three pairs of methods: get
and set
for setting values, enable
and disable
for toggling boolean options, and enabled
and disabled
for testing boolean options. Options can be set based on the current environment by using the configure
method.
Here’s an example of these methods:
var express = require('express');
var app = express();
var assert = require('assert');
app.set('title', 'DailyJS');
assert.equal(app.get('title'), 'DailyJS');
app.configure('production', 'staging', function() {
// 'emails' is an internal setting I've made up
// It could be used to only send emails from certain environments
app.enable('emails');
assert(app.enabled('emails'));
});
app.configure('test', function() {
app.disable('emails');
assert(app.disabled('emails'));
});
The configure
method is based on process.env.NODE_ENV
, which is available in app.get('env')
. If you access it through app.get
you’ll see a default of 'development'
rather than undefined
. When you deploy your application you’ll want to make sure the NODE_ENV
environmental variable is set to staging
or production
. How this is done is based on operating system or cloud provider – with Heroku it would be heroku config:add NODE_ENV=production
.
These methods are useful, but sometimes you want to store settings in configuration files. It depends on the type of project you’re working on, but most of the commercial projects I’ve worked on required configuration files.
I use JSON as the format for these files because it’s easy to write and parse in Node projects. You don’t even need to use JSON.parse
, you can just use require
. I like to use a configuration file for each environment, so I usually end up with a directory like this:
config/development.json
config/production.json
config/test.json
You can load one of these files with require('config/development.json')
, but you can go a step further by using an index.js
file:
module.exports = {
development: require('./development.json'),
production: require('./production.json'),
test: require('./test.json')
};
Now you can use var config = require('./config')
elsewhere in your project. However, because process.env.NODE_ENV
gets set, we can simplify that index.js
file even further:
module.exports = require('./' + (process.env.NODE_ENV || 'development') + '.json');
Now require('./config')
will return an object that contains the configuration for the current environment. I use this to do things like turn off AWS emails in my unit tests, but leave them on for the production system. By exploiting the design of Node’s module system you basically get configuration files for free.
This might not be the best solution for every project. The config module by Loren West supports YAML files, and nconf from flatiron is hierarchical – settings can be passed in as command-line options, from the environment, or from a file, and used based on precedence. It can also store settings in databases like Redis.
How do you configure your Express projects?
Read more https://feedproxy.google.com/~r/dailyjs/~3/oZcU32SrNDs/recipe-for-express-configuration
Page 837 of 1311