“ into the Link URL field in the Insert/edit link dialog box, insert a “mailto:” link. That is, “mailto:” plus your email address. For example, “mailto:name@example.com”
Blog
-
Comments box not available in IE
In internet explorer the comments box is not available, cannot put in text. The same feature works in Firefox and Chrome, independent of the WYSIWYG module being enabled.
-
Email notifications
For the site to process notifications of updates the email queue needs to be emptied out. This is usually done by setting up cron jobs. An alternative to cron jobs is poormanscron, a module that emulates cron using a Java script.
Additionally, make sure to tick the box: "notofy poster of own posts' and disabel debugging in the notofications settings:
(1) Install module Poormanscron
(2) Go to /admin/messaging/notifications
- Tick 'Notify user of won postings' i
- Untick 'Enable debugging'
- Set everything to 'immediately'
- (optional) 'Logging' set to 16 weeks
-
Hiding posts on the WordPress blog
Recently it was pointed out that the blog displayed old vacancies under the catgeory tab jobs: http://icardablog.wordpress.com/category/jobs/
WordPress does not offer a feature to simply 'unpublish' posts, however there are many plugins that can achieve that effect.We don't want to simplky delete old posts, but need to archivew them.
The simple and dirty solution is to set posts to 'private', this can even be done via the quick edit menu. This means they will reamin visible to administrators only, but will be hidden from view for most other users.
-
From development to production environement
A typical website desing process happens on several machines in parallel, particularly when multiple developers are involved. We are not yet following best practices in all these areas and should improve the overall workflow. Particularly drupal featurees module would make versioning and reusing of the code much less time consuming.
- Developing environment: every developer has a version of the website installed locally on their machine.
- Staging environment: This is online and serves as the 'stage' where the client can test the site
- Production environment: This is the actual web site, not the place to test out new things.
Best practices include using a VNS (Version Control System) to be able to roll back the code and using the Drush module: makes updaing drupal simpler via the command line.
Here are some good reads:
https://community.openatrium.com/documentation-en/node/1943