rev.dennis

Are you trying to figure out why you might be getting the error Error: Could not load template 'feed__generic_12' from group '' It appears you may have been looking at one of the Blocks in IP.Content and somehow just looking at it may have changed something. For me it was on the Home Page or Front Page and the error mentions feed and I know normally that this spot it should be the Forum Recent Topics. So I went to that block and clicked Edit.. under the Template tab it showed nothing for a preview so I knew that was an issue. I selected News Feed and it showed a preview so I clicked save and my error went away.

The sed program is a stream editor, and is designed to apply the actions from a script to each line (or, more generally, to specified ranges of lines) of the input file or files. Its language is based on ed, the Unix editor, and although it has conditionals and so on, it is hard to work with for complex tasks. You can work minor miracles with it - but at a cost to the hair on your head. However, it is probably the fastest of the programs when attempting tasks within its remit. (It has the least powerful regular expressions of the programs discussed - adequate for many purposes, but certainly not PCRE - Perl-Compatible Regular Expressions) The awk program (name from the initials of its authors - Aho, Weinberger and Kernighan) is a tool originally for formatting reports. It can be used as a souped up sed; in its more recent versions, it is computationally complete. It uses an interesting idea - the program is based on 'patterns matched' and 'actions taken when the pattern matches'. The patterns are fairly powerful (Extended Regular Expressions). The language for the actions is similar to C. One of the key features of awk is that it splits the input lines into fields automatically. Perl was written in part as an awk-killer and sed-killer. Two of the programs provided with it are a2p and s2p for converting awk scripts and sed scripts into Perl. Perl is one of the earliest of the next generation of scripting languages (Tcl/Tk can probably claim primacy). It has powerful integrated regular expression handling with a vastly more powerful language. It provides access to almost all system calls, and has the extensibility of the CPAN modules. (Neither awk nor sed is extensible.) One of Perl's mottos is "TMTOWTDI - There's more than one way to do it" (pronounced "tim-toady"). Perl has 'objects', but it is more of an add-on than a fundamental part of the language. Python was written last, and probably in part as a reaction to Perl. It has some interesting syntactic ideas (indenting to indicate levels - no braces or equivalents). It is more fundamentally object-oriented than Perl; it is just as extensible as Perl. OK - when to use each? sed - when you need to do simple text transforms on files. awk - when you only need simple formatting and summarization or transformation of data. perl - for almost any task, but especially when the task needs complex regular expressions. python - for the same tasks that you could use Perl for. I'm not aware of anything that Perl can do that Python can't, nor vice versa. The choice between the two would depend on other factors. Python has less accreted syntax and is generally somewhat simpler to learn. sed example. Replace every word that matches ugly with beautiful in lover.txt $ sed -i 's/ugly/beautiful/g' /home/dennis/friends/lover.txt awk example. Basic awk command looks like this. Take each line of the input file; if the line contains the pattern apply the action to the line and write the resulting line to the output-file. If the pattern is omitted, the action is applied to all line. awk 'pattern {action}' input-file > output-file perl example. This reads from the standard input and counts the number lines which are blank, and lines which are entirely perl-style # comments (begin with # as the first non-blank character.) It reports these figures. use strict; # Counters to return. my $nblank = 0; my $ncomm = 0; # Read each line into the variable $line. while(my $line = ) { if($line =~ /^s*$/) { ++$nblank; } if($line =~ /^s*#/) { ++$ncomm; } } print "$nblank blank lines, $ncomm comments.n"; python example.

The sed program is a stream editor, and is designed to apply the actions from a script to each line (or, more generally, to specified ranges of lines) of the input file or files. Its language is based on ed, the Unix editor, and although it has conditionals and so on, it is hard to work with for complex tasks. You can work minor miracles with it - but at a cost to the hair on your head. However, it is probably the fastest of the programs when attempting tasks within its remit. (It has the least powerful regular expressions of the programs discussed - adequate for many purposes, but certainly not PCRE - Perl-Compatible Regular Expressions) The awk program (name from the initials of its authors - Aho, Weinberger and Kernighan) is a tool originally for formatting reports. It can be used as a souped up sed; in its more recent versions, it is computationally complete. It uses an interesting idea - the program is based on 'patterns matched' and 'actions taken when the pattern matches'. The patterns are fairly powerful (Extended Regular Expressions). The language for the actions is similar to C. One of the key features of awk is that it splits the input lines into fields automatically. Perl was written in part as an awk-killer and sed-killer. Two of the programs provided with it are a2p and s2p for converting awk scripts and sed scripts into Perl. Perl is one of the earliest of the next generation of scripting languages (Tcl/Tk can probably claim primacy). It has powerful integrated regular expression handling with a vastly more powerful language. It provides access to almost all system calls, and has the extensibility of the CPAN modules. (Neither awk nor sed is extensible.) One of Perl's mottos is "TMTOWTDI - There's more than one way to do it" (pronounced "tim-toady"). Perl has 'objects', but it is more of an add-on than a fundamental part of the language. Python was written last, and probably in part as a reaction to Perl. It has some interesting syntactic ideas (indenting to indicate levels - no braces or equivalents). It is more fundamentally object-oriented than Perl; it is just as extensible as Perl. OK - when to use each? sed - when you need to do simple text transforms on files. awk - when you only need simple formatting and summarization or transformation of data. perl - for almost any task, but especially when the task needs complex regular expressions. python - for the same tasks that you could use Perl for. I'm not aware of anything that Perl can do that Python can't, nor vice versa. The choice between the two would depend on other factors. Python has less accreted syntax and is generally somewhat simpler to learn. sed example. Replace every word that matches ugly with beautiful in lover.txt $ sed -i 's/ugly/beautiful/g' /home/dennis/friends/lover.txt awk example. Basic awk command looks like this. Take each line of the input file; if the line contains the pattern apply the action to the line and write the resulting line to the output-file. If the pattern is omitted, the action is applied to all line. awk 'pattern {action}' input-file > output-file perl example. This reads from the standard input and counts the number lines which are blank, and lines which are entirely perl-style # comments (begin with # as the first non-blank character.) It reports these figures. use strict; # Counters to return. my $nblank = 0; my $ncomm = 0; # Read each line into the variable $line. while(my $line = ) { if($line =~ /^s*$/) { ++$nblank; } if($line =~ /^s*#/) { ++$ncomm; } } print "$nblank blank lines, $ncomm comments.n"; python example.

This has been a big problem of mine as well. If I figure out something, I'll post it here. It doesn't seem its as easy as a change in the template or something. From what I've been reading its as serious as changing individual files which would be not the smartest move.

This has been a big problem of mine as well. If I figure out something, I'll post it here. It doesn't seem its as easy as a change in the template or something. From what I've been reading its as serious as changing individual files which would be not the smartest move.

Does anyone know how to customize the login screen for Open Atrium 2? Actually if you could also tell me how to customize the footer would be helpful also. Currently trying to deploy Open Atrium 2 at work but we can't be advertising for Open Atrium all over the place. Any help would be most appreciated.

Does anyone know how to customize the login screen for Open Atrium 2? Actually if you could also tell me how to customize the footer would be helpful also. Currently trying to deploy Open Atrium 2 at work but we can't be advertising for Open Atrium all over the place. Any help would be most appreciated.

These are good instructions

These are good instructions

Thank You but I couldn't keep up. It appears with almost every other release of Open Atrium 2 the menu names change. So the documentation or instructions aren't accurate anymore after a few updates. I'm still learning OA2 myself.

Thank You but I couldn't keep up. It appears with almost every other release of Open Atrium 2 the menu names change. So the documentation or instructions aren't accurate anymore after a few updates. I'm still learning OA2 myself.

Here are some steps (not positive they are exact but it should get you close) Click ADMIN - Structure - Taxonomy - Add vocabulary (what categories/titles for terms.. example Status) Click add terms right next to your Vocabulary name you just created (example next to Status) and type a Name for your first term.. under Status a term I'm adding is Active (the description is optional) and I leave everything else with default settings so I don't do anything with Relations (Parent terms: , Weight: 0) and I leave URL path settings alone (Generate automatic URL alias is checked by default) then click Save. Repeat for each term you want to add to that vocabulary. Add multiple Vocabulary Names. Now let's apply these to a space... click on the space you want to apply them to. Top right there is a gear icon, click on the gear icon then click on Config Click on Taxonomy Expand the Existing vocabularies to show the newly created vocabularies. Place a checkmark next to each vocabulary you want to apply to this space (and sub-spaces by default) and click save. Now that the vocabulary moved from Existing up to the default display, click on edit vocabulary next to the vocabulary you added. Scroll down to where you see Node - Space and place a checkmark in the Enable box. I also would change the Widget type to Check boxes/radio buttons and select how many values are acceptable. Click Save. Now go to your space and click the edit button and make the choices for that taxonomy that should apply to that space... you should see it towards the bottom... click save. To have this term show up on the space for anyone browsing... while viewing the space, click Customize this page. On the sidebar (as a suggestion... you can pick anywhere in your layout) click the + button. On the left, click Page Content Scroll down until you see Node terms, and click +Add I usually click Override title and enter the title of my Vocabulary (like Status as used in my example above) Under Vocabulary selection, I choose my vocabulary Status and click Save. That's all there is to it (pretty sure). Hope that helps

Here are some steps (not positive they are exact but it should get you close) Click ADMIN - Structure - Taxonomy - Add vocabulary (what categories/titles for terms.. example Status) Click add terms right next to your Vocabulary name you just created (example next to Status) and type a Name for your first term.. under Status a term I'm adding is Active (the description is optional) and I leave everything else with default settings so I don't do anything with Relations (Parent terms: , Weight: 0) and I leave URL path settings alone (Generate automatic URL alias is checked by default) then click Save. Repeat for each term you want to add to that vocabulary. Add multiple Vocabulary Names. Now let's apply these to a space... click on the space you want to apply them to. Top right there is a gear icon, click on the gear icon then click on Config Click on Taxonomy Expand the Existing vocabularies to show the newly created vocabularies. Place a checkmark next to each vocabulary you want to apply to this space (and sub-spaces by default) and click save. Now that the vocabulary moved from Existing up to the default display, click on edit vocabulary next to the vocabulary you added. Scroll down to where you see Node - Space and place a checkmark in the Enable box. I also would change the Widget type to Check boxes/radio buttons and select how many values are acceptable. Click Save. Now go to your space and click the edit button and make the choices for that taxonomy that should apply to that space... you should see it towards the bottom... click save. To have this term show up on the space for anyone browsing... while viewing the space, click Customize this page. On the sidebar (as a suggestion... you can pick anywhere in your layout) click the + button. On the left, click Page Content Scroll down until you see Node terms, and click +Add I usually click Override title and enter the title of my Vocabulary (like Status as used in my example above) Under Vocabulary selection, I choose my vocabulary Status and click Save. That's all there is to it (pretty sure). Hope that helps

Not able to apply taxonomy to Spaces. I know I must be doing something wrong but can't seem to figure it out. Any help is most appreciated.

Not able to apply taxonomy to Spaces. I know I must be doing something wrong but can't seem to figure it out. Any help is most appreciated.

Here are the instructions and any hiccups or notes in regards to upgrading Open Atrium This is the recommended way of updating a standard Open Atrium distribution to ensure that Drupal core files are updated along with the Open Atrium distribution: 0) Backup Before starting the upgrade you should backup your all your code and your database. This is essential, so you can roll-back if something goes wrong during the update! # cp -avr /var/www/oa/ /var/www/oaBACKUP 1) Save the /sites directory The /sites directory contains all your site-specific customisation. So save this directory so that we can re-upload it in a later step. # cp -avr /var/www/oa/sites/ /var/www/oaBACKUP/ 2) Download the new files Download the latest version of Open Atrium from project page: https://www.drupal.org/project/openatrium 3) Upload the new files Replace the site's entire codebase with the new files. Do this by deleting the entire contents of the web root directory - the directory Open Atrium is installed in - completely, and then upload all the new files in their place. Note: Do not simply copy the new files on top of the old ones. This will not delete old files that are no longer used and this could cause issues. You should have your old web root backed-up just in case! # rm -rf /var/www/oa/ # tar -zxvf openatrium-7.x-2.23-core.tar.gz -C /var/www/ # mv /var/www/openatrium-7.x-2.23/ /var/www/oa/ 4) Replace the /sites directory Move or copy the /sites folder you saved in step 1 into the /sites folder of your new code. # cp -avr /var/www/oaBACKUP/sites/ /var/www/oa/ Don't forget to correct permissions (not sure this is correct thing to do but I did it) # chown -R www-data:www-data /var/www # chmod -R g+rw /var/www 5) Run updates Run update.php on your site: http://youropenatriumsite.com/update.php Or with drush: drush updb This will perform essential tasks to bring your database up-to-date with the latest version (if there are any). 6) Clear caches Clear the Drupal cache at: Admin - Configuration - Development - Performance - Clear all caches Or with drush: drush cc all Note: If you get errors then you may need to rebuild your registry. This is sometimes necessary if modules have moved around during the update. You can rebuild your registry with or without drush by following the instructions on the project page: https://www.drupal.org/project/registry_rebuild 7) Revert features Take extra caution here. drush fra -y (Read notes first) This command is required to update all of Open Atrium's features to the latest version. Running it will revert and overwrite any existing features, including any changes that you may have made to Open Atrium's configuration. It is therefore very important to capture any customization using Features Override before attempting to upgrade. This command can be run at any other time to restore Open Atrium's features to their default settings (Eg: if someone has inadvertently tampered with any Views or layouts within Open Atrium). 8) Done Your site is now up-to-date. Test it out! --- Advanced notes Updating the latest -dev version (for expert Drupal devs) If you built your site using "git" and "drush" then you can use these same tools to update your site. First, save a copy of your Drupal sites/ directory as this will be overwritten by the update process. Next, go to the "openatrium" folder where you initially used "git" to fetch the Open Atrium repository. Use "git pull" to retrieve the latest version of the distribution. Then run the ./build.sh or ./build-dev.sh script exactly as before. Instead of pointing these scripts to your root web directory, you can point them to a temp directory in case the installation fails. The build.sh scripts delete everything in the target directory so building to a temp directory prevents your current web site from being lost if the build fails. Once the build is successful you can move the temporary directory in place of your web root, then restore the /sites directory that you previously saved. If you just need to make a quick update of a specific open atrium module, you can also just go to that module directory and use "git pull origin" to pull in the latest changes without rebuilding the entire distribution.

Here are the instructions and any hiccups or notes in regards to upgrading Open Atrium This is the recommended way of updating a standard Open Atrium distribution to ensure that Drupal core files are updated along with the Open Atrium distribution: 0) Backup Before starting the upgrade you should backup your all your code and your database. This is essential, so you can roll-back if something goes wrong during the update! # cp -avr /var/www/oa/ /var/www/oaBACKUP 1) Save the /sites directory The /sites directory contains all your site-specific customisation. So save this directory so that we can re-upload it in a later step. # cp -avr /var/www/oa/sites/ /var/www/oaBACKUP/ 2) Download the new files Download the latest version of Open Atrium from project page: https://www.drupal.org/project/openatrium 3) Upload the new files Replace the site's entire codebase with the new files. Do this by deleting the entire contents of the web root directory - the directory Open Atrium is installed in - completely, and then upload all the new files in their place. Note: Do not simply copy the new files on top of the old ones. This will not delete old files that are no longer used and this could cause issues. You should have your old web root backed-up just in case! # rm -rf /var/www/oa/ # tar -zxvf openatrium-7.x-2.23-core.tar.gz -C /var/www/ # mv /var/www/openatrium-7.x-2.23/ /var/www/oa/ 4) Replace the /sites directory Move or copy the /sites folder you saved in step 1 into the /sites folder of your new code. # cp -avr /var/www/oaBACKUP/sites/ /var/www/oa/ Don't forget to correct permissions (not sure this is correct thing to do but I did it) # chown -R www-data:www-data /var/www # chmod -R g+rw /var/www 5) Run updates Run update.php on your site: http://youropenatriumsite.com/update.php Or with drush: drush updb This will perform essential tasks to bring your database up-to-date with the latest version (if there are any). 6) Clear caches Clear the Drupal cache at: Admin - Configuration - Development - Performance - Clear all caches Or with drush: drush cc all Note: If you get errors then you may need to rebuild your registry. This is sometimes necessary if modules have moved around during the update. You can rebuild your registry with or without drush by following the instructions on the project page: https://www.drupal.org/project/registry_rebuild 7) Revert features Take extra caution here. drush fra -y (Read notes first) This command is required to update all of Open Atrium's features to the latest version. Running it will revert and overwrite any existing features, including any changes that you may have made to Open Atrium's configuration. It is therefore very important to capture any customization using Features Override before attempting to upgrade. This command can be run at any other time to restore Open Atrium's features to their default settings (Eg: if someone has inadvertently tampered with any Views or layouts within Open Atrium). 8) Done Your site is now up-to-date. Test it out! --- Advanced notes Updating the latest -dev version (for expert Drupal devs) If you built your site using "git" and "drush" then you can use these same tools to update your site. First, save a copy of your Drupal sites/ directory as this will be overwritten by the update process. Next, go to the "openatrium" folder where you initially used "git" to fetch the Open Atrium repository. Use "git pull" to retrieve the latest version of the distribution. Then run the ./build.sh or ./build-dev.sh script exactly as before. Instead of pointing these scripts to your root web directory, you can point them to a temp directory in case the installation fails. The build.sh scripts delete everything in the target directory so building to a temp directory prevents your current web site from being lost if the build fails. Once the build is successful you can move the temporary directory in place of your web root, then restore the /sites directory that you previously saved. If you just need to make a quick update of a specific open atrium module, you can also just go to that module directory and use "git pull origin" to pull in the latest changes without rebuilding the entire distribution.

Postfix is great and highly recommended versus others. It's simple to use but can be very advanced if need be. When referencing postfix and nagios then think of postfix as a relay for the client, nagios. Some configuration notes... (may not be complete) If you want to receive email notifications for Nagios alerts, you need to install the mailx (Postfix) package. sudo apt-get install mailx sudo apt-get install postfix Test your mail relay (postfix) to see if it's working echo "Test Message" | mail -s "subject" [email protected] Something kinda neat, if you prefer to test using a From address of [email protected] you would enter this command instead echo "testing" | mail -s "haha" [email protected] -- -f [email protected] If successful, double check the valid path for mail by running which mail Also you can look in the maillog file to see what was used successfully to send mail cat /var/log/maillog Configure Nagios to send mail using your mail relay (postfix) edit /usr/local/nagios/etc/objects/commands.cfg If you found that which mail command above shows your mail client is in a different location than /bin/mail you need to search the cfg for all /bin/mail statements and replace with the location of mail for your system. Restart Nagios sudo /etc/init.d/nagios restart edit commands.cfg note this is assuming your mail is at /bin/mail, if its different change that # 'notify-host-by-email' command definition define command{ command_name notify-host-by-email command_line /usr/bin/printf "%b" "***** Nagios *****nnNotification Type: $NOTIFICATIONTYPE$nHost: $HOSTNAME$nState: $HOSTSTATE$nAddress: $HOSTADDRESS$nInfo: $HOSTOUTPUT$nnDate/Time: $LONGDATETIME$n" | /bin/mail -s "** $NOTIFICATIONTYPE$ Host Alert: $HOSTNAME$ is $HOSTSTATE$ **" $CONTACTEMAIL$ } # 'notify-service-by-email' command definition define command{ command_name notify-service-by-email command_line /usr/bin/printf "%b" "***** Nagios *****nnNotification Type: $NOTIFICATIONTYPE$nnService: $SERVICEDESC$nHost: $HOSTALIAS$nAddress: $HOSTADDRESS$nState: $SERVICESTATE$nnDate/Time: $LONGDATETIME$nnAdditional Info:nn$SERVICEOUTPUT$n" | /bin/mail -s "** $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **" $CONTACTEMAIL$ } Next you need to add contact info so edit contact.cfg. Just change the admin to your email address to test things out. The group stuff isn't as straight forward as you think and everything defaults to sending to the admin so if admin was your email address you'll get emails.

Postfix is great and highly recommended versus others. It's simple to use but can be very advanced if need be. When referencing postfix and nagios then think of postfix as a relay for the client, nagios. Some configuration notes... (may not be complete) If you want to receive email notifications for Nagios alerts, you need to install the mailx (Postfix) package. sudo apt-get install mailx sudo apt-get install postfix Test your mail relay (postfix) to see if it's working echo "Test Message" | mail -s "subject" [email protected] Something kinda neat, if you prefer to test using a From address of [email protected] you would enter this command instead echo "testing" | mail -s "haha" [email protected] -- -f [email protected] If successful, double check the valid path for mail by running which mail Also you can look in the maillog file to see what was used successfully to send mail cat /var/log/maillog Configure Nagios to send mail using your mail relay (postfix) edit /usr/local/nagios/etc/objects/commands.cfg If you found that which mail command above shows your mail client is in a different location than /bin/mail you need to search the cfg for all /bin/mail statements and replace with the location of mail for your system. Restart Nagios sudo /etc/init.d/nagios restart edit commands.cfg note this is assuming your mail is at /bin/mail, if its different change that # 'notify-host-by-email' command definition define command{ command_name notify-host-by-email command_line /usr/bin/printf "%b" "***** Nagios *****nnNotification Type: $NOTIFICATIONTYPE$nHost: $HOSTNAME$nState: $HOSTSTATE$nAddress: $HOSTADDRESS$nInfo: $HOSTOUTPUT$nnDate/Time: $LONGDATETIME$n" | /bin/mail -s "** $NOTIFICATIONTYPE$ Host Alert: $HOSTNAME$ is $HOSTSTATE$ **" $CONTACTEMAIL$ } # 'notify-service-by-email' command definition define command{ command_name notify-service-by-email command_line /usr/bin/printf "%b" "***** Nagios *****nnNotification Type: $NOTIFICATIONTYPE$nnService: $SERVICEDESC$nHost: $HOSTALIAS$nAddress: $HOSTADDRESS$nState: $SERVICESTATE$nnDate/Time: $LONGDATETIME$nnAdditional Info:nn$SERVICEOUTPUT$n" | /bin/mail -s "** $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **" $CONTACTEMAIL$ } Next you need to add contact info so edit contact.cfg. Just change the admin to your email address to test things out. The group stuff isn't as straight forward as you think and everything defaults to sending to the admin so if admin was your email address you'll get emails.

Sometimes that ALOM port gets hung up and won't respond. From you linux/unix/solaris operating system try and run: scadm resetrsc -s

Sometimes that ALOM port gets hung up and won't respond. From you linux/unix/solaris operating system try and run: scadm resetrsc -s

Okay, so I installed Open Atrium and have been trying to enable clean URL's and I'm having nothing but issues. Currently when I launch my site (whateversite.com) I get Now if I add ?q=user at the end (whateversite.com/?q=user) it will send me to the annoying default open Atrium login page <-- if anyone knows how to change this I would very much appreciate it) Any idea on how to fix the clean URL issue with Open Atrium When I click the "Run the clean URL test" it responds with The clean URL test failed. The online handbook it references doesn't seem to fix the issue.

Okay, so I installed Open Atrium and have been trying to enable clean URL's and I'm having nothing but issues. Currently when I launch my site (whateversite.com) I get Now if I add ?q=user at the end (whateversite.com/?q=user) it will send me to the annoying default open Atrium login page <-- if anyone knows how to change this I would very much appreciate it) Any idea on how to fix the clean URL issue with Open Atrium When I click the "Run the clean URL test" it responds with The clean URL test failed. The online handbook it references doesn't seem to fix the issue.

Second time mySQL went down. I'm currently on the Power Plan (which is a shared hosting plan) which means I share a server with a bunch of other people which one of these people is bringing the mySQL services down on this shared server. First outage a few weeks ago was for about an hour, this time services resumed in about 20minutes which feels like a lifetime when you rely on the site to be up for everyone to use, especially when I have several sites dedicated for my clients/customers. I believe I am going to have to bite the bullet and upgrade to VPS (Virtual Private Server)

Second time mySQL went down. I'm currently on the Power Plan (which is a shared hosting plan) which means I share a server with a bunch of other people which one of these people is bringing the mySQL services down on this shared server. First outage a few weeks ago was for about an hour, this time services resumed in about 20minutes which feels like a lifetime when you rely on the site to be up for everyone to use, especially when I have several sites dedicated for my clients/customers. I believe I am going to have to bite the bullet and upgrade to VPS (Virtual Private Server)