Oznaka: extensions

We have just released a new version of eZ Tags extension which brings the version number up to 1.2. This is a second version released since the initial blog post introducing eZ Tags six months ago and we thought it would be a good idea to give an overview of what is new in eZ Tags 1.1 and 1.2.

Since we tagged eZ Tags extension as stable on GitHub few weeks ago, we thought this would be a good time to write something about how to install eZ Tags extension and common usages.

The time has come to inform the eZ community about interesting stuff currently in development in eZ Tags extension and to give a current overview of the project.

Social networks are what web is about today. If you don’t have at least one social network account, you practically don’t exist on the Internet. Some would argue about these statements (including myself, mainly concerning Facebook), but at the end of the day, the truth is that social networks matter, to users as well as websites.

Netgen Push provides a simple and effective way to push any kind of content from eZ Publish to various social networks. For the time being, Twitter and Facebook connectors are implemented, while eZ Publish REST API and Tumblr API are in the planning stage. Netgen Push also provides a basic framework to develop your own connectors to any social network that uses OAuth authentication protocol.

We introduce some of the details on how we developed "Netgen Suggest" extension for eZPublish. Extension is shared with community: projects.ez.no/ngsuggest. Download and installation instructions can be found there.

Here is just a short technical explanation of the topic in the last blog post. That post described how we solved a performance issue on one eZ Publish based web site by developing an eZ Publish extension which overrides eZMutex to use memcache instead of file locking. The extension is published and shared with the community on projects.ez.no.

The post is describing how we solved a performance issue on one eZ Publish based web site. The site was using more web servers with shared disk device based on SAN. With no obvious reason web servers had high load averages and what was even worse: increasing load on one web server would quickly increase load on other web servers...