When I first started with Drupal 7 I did not really know what this term meant so I just avoided that part of the setup. Of course as time went on, and I started to brave things like views, I started to want to group specific articles and pages so that I could list them using Views. Suddenly the relevance became clear. You need to tag / reference the article when you write it.
The standard installation of Drupal 7 comes with 'Article' as a content type and that has the ability to add tags, so basically one can tag an article and then list numerous articles by their tags using Views.
Taxonomy
So, firstly, you go to Structure / taxonomy where you are given the option to add a taxonomy term - either a new term or a subset of the existing terms - one of which is tag. To add a new tag, you simply 'add a term' under tags. Tags are useful for the standard 'Article' provided by Drupal 7 but are limited by the way you input them when adding them to the 'Article'
My preference is to use a reference specific to your site. Typically, I will use the shortened site name and add sub-references such as 'news' or 'issues' etc. These may also have many sub-levels if you want to add them, so when you make use of them, you can choose a level and everything below that also applies. For more detail :
Tagging an Article
If you want to tag an 'article' then you need to add terms under tags. One of the down sides of the standard 'article' content type is that it uses the 'type in a letter' system so if you don't know what you're looking for, it probably won't get tagged. Generally, I prefer to avoid making modifications to the standard content types and adding my own.
Adding a Content Type
This is a fairly straightforward procedure, and if you expect less computer literate people to be making use of your back end, its a very good way of limiting them to the features that you want them to see. Go to Structure / Content Types and add a content type. You can then decide for yourself what you want to use there -
You may or may not want the article to be promoted to the front page, or for the writer's name to be included there. Comment settings may be modified in advance as well as menu settings. This allows you to limit what the end user can do under permissions.
Adding a Reference Check Box to your Content Type
One of the big bonuses of adding your own content type is that you can add stuff to it without messing with the original 'Article' or 'Basic Page' content types. Effectively you can add a field for references which means that your end user just has to select a box to choose what type of article has been written.
Click on the 'Manage Fields' tag while editing your content type and add a new field. Give it a name (such as reference) and under 'field type' use 'term reference'. Under 'widget type' you can now decide if you want check boxes etc. Once you've chosen that, you will also be given the option of deciding what level of your reference tree you want to be made available to the user
For a full description with sexy screen shots go to http://www.drupalgardens.com/documentation/taxonomy/content .
Drupal
Starting in January 2011, I decided to learn Drupal Innocently believing all the promises of operational modules after almost a year, I am only a little the wiser.... These are some notes
Thursday, January 8, 2015
Monday, September 8, 2014
Themes
The purpose of this post is to both remind myself (brain cells don't retain stuff as well as they used to) and to give a heads up for others on the various themes that are available for Drupal.
I am currently putting together a new site for Nauticat Charters so I need to find a theme that they will be happy with.
My belief is that for tourism sites, there is a need for lots of images. The fact is that people don't read the content unless they are attracted to what they see on the site.
I find this part of putting together a site the most challenging because of the huge number of possibilities available and how you do it is very personal. Themes come in all shapes and sizes. The starting point (because there has to be one) is http://drupal.org/project/Themes.
What to consider
To make matters worse, there are a number of 'base' themes that act as the basis for other themes. Typical examples are the ones that you find on the first page such as Adaptive Theme, Zen, Omega and Fusion. Adaptive pops up frequently as does Zen. Omega less so.
There are questions to ask before you decide on a theme which will also help you narrow it down:
Slideshow Themes
As I mentioned above, my current project is a tourism site that I feel requires at last one slideshow - on the front page. When looking for a theme that you like, don't feel that you are tied to only having to use themes that offer slide shows. At the end of the day, what those sites are probably doing is applying a slide show within the site anyway, so there is nothing stopping you choosing a theme that does not have a slide show and then adding one. I put together a technical site :
www.innomark.co.za where I built a slider using Views Slideshow which could then be added to any block.
This said, if the theme is designed to have a slide show and has the instructions to include it, why not go with that option.
www.marlinspike.co.za is a straight take on the Blue Masters theme and it worked very well. I was particularly attracted to this one because it aslo offered names and links on the images which can be useful to allow your user to go quickly to a destination.
For www.llandudnosportsclub.co.za, I used Danland which provided a straightforward large cycling display and a theme that provides good seo and ease of use.
For this web site, I'm found a new theme called andromeda
I am currently putting together a new site for Nauticat Charters so I need to find a theme that they will be happy with.
My belief is that for tourism sites, there is a need for lots of images. The fact is that people don't read the content unless they are attracted to what they see on the site.
I find this part of putting together a site the most challenging because of the huge number of possibilities available and how you do it is very personal. Themes come in all shapes and sizes. The starting point (because there has to be one) is http://drupal.org/project/Themes.
What to consider
To make matters worse, there are a number of 'base' themes that act as the basis for other themes. Typical examples are the ones that you find on the first page such as Adaptive Theme, Zen, Omega and Fusion. Adaptive pops up frequently as does Zen. Omega less so.
There are questions to ask before you decide on a theme which will also help you narrow it down:
- Where do you need your regions?
Many of the themes offer a highly complex set up of regions and some offer the option of modifying these - but if you are putting together a basic site, you may only need a main region and two sidebars. Do you actually need regions. Many people make web sites using panels which effectively give regions to your regions and if set up properly do away with the need for standard regions all together.
- Is it important to have html5
HTML5 offers the facility to use many newer features mostly relating to the handling of images. If this isn't important, it may not be essential to have this funcionality, but remember that the site could need modification in a couple of years and not having it may need that you need to change your theme in the future.
- Mobile Access
Currently this isn't a major issue for many people, but this is likely to change radically over the next few years. Implementation using mobile devices is a whole area in itself and includes the question as to whether you should or shouldn't have two distinct sites - one mobile and one not linking to the same database.
- SEO (Search Engine Optimization)
The way that search engines read the information on your site is important and what they see first could effect your position. Search engines still see text, which is why flash sites are no longer fashionable and having a structured site is essential.
- Fluid or Fixed
Some web sites will take up the whole of your screen regardless of the size of your screen. This means that they may look different depending on the screen size. but that they do fill up all of the real estate. These are called Fluid sites. Many people prefer to stick to a standard 12/16 column grid allowing them to set up regions more easily.
Slideshow Themes
As I mentioned above, my current project is a tourism site that I feel requires at last one slideshow - on the front page. When looking for a theme that you like, don't feel that you are tied to only having to use themes that offer slide shows. At the end of the day, what those sites are probably doing is applying a slide show within the site anyway, so there is nothing stopping you choosing a theme that does not have a slide show and then adding one. I put together a technical site :
www.innomark.co.za where I built a slider using Views Slideshow which could then be added to any block.
This said, if the theme is designed to have a slide show and has the instructions to include it, why not go with that option.
www.marlinspike.co.za is a straight take on the Blue Masters theme and it worked very well. I was particularly attracted to this one because it aslo offered names and links on the images which can be useful to allow your user to go quickly to a destination.
For www.llandudnosportsclub.co.za, I used Danland which provided a straightforward large cycling display and a theme that provides good seo and ease of use.
For this web site, I'm found a new theme called andromeda
Wednesday, March 20, 2013
Installing WAMP or XAMPP and Drupal
WAMP Installation
This post is dedicated to the new installation of a web site. Haven't done it for a while, so most of my software (previously downloaded) is out of date.
The first step is to get your requirements. In the old days, you would go to the customer and get some information and put together a detailed specification that the customer would then sign off on. I prefer to speak to the customer to get an idea of what she wants and then put a basic site together so that early on in the process, she has an idea of what she is getting. Of course one of the advantages of drupal is that this is easily changed.
Next step is to set up your offline web site. To do this I use WAMP (Windows, Apache, MySQL and PHP). It turns out that my version is way out of date and when I uploaded and installed the new version over the old one, it didn't work. Major problem. I simply removed the previous version and changed the name of the Wamp folder to wampold and started from scratch.
Once installed, you can check two things. going to local host in your browser and coming up with the home page proves that you have connected to the server. Next you need to get PHPmyAdmin going. In my case I got a '2002' error telling me that I had been rejected:
#2002 - No connection could be made because the target machine actively refused it.
While the solution could be skype (try stopping it), this is the best answer I found and the one that worked for me:
left click wampmanager icon -> Apache -> httpd.conf
this will launch notpad to edit the Apache config file
Look for 'Listen' and change it to 'Listen 0.0.0.0:80'
reboot the software
Found the answer at this site:
http://forum.wampserver.com/read.php?2,110318
So finally having got the server going, go to PHPmyadmin and open a new empty database (with the name of your new site) and set up an admin user with a password..
Now you download the latest version of Drupal, make directory under wamp/www with the name of you new site and unzip drupal files (not the file name) into this site.
Go to your browser and type localhost/[new site name] and follow the installation instructions.
XAMPP
XAMPP is similar to WAMP in that it is a server that you set up on a Windows machine. I found that it was less intuitive, but more likely to work. I tried to get WAMP working again recently and failed.
Like WAMP, you simply download it and run it. Unlike WAMP, you have to start the various part manually. The two that are important are Apache and MySQL. PHP is also included but not in the control panel (which is a little irritating, but not a train smash). Once again, in order to set it up properly, I had to change the Apache port (using the config button) to 2375 (recommended) instead of port 80. The down side of this is that you have to go to localhost:2375 to find the main page of the server and localhost:2375/yourwebsite to get to your web site.
If you are using Drupal, there is one other trick that I only learned much later (which I couldn't edit my content types in Drupal) and this is probably applicable to WAMP as well.
This post is dedicated to the new installation of a web site. Haven't done it for a while, so most of my software (previously downloaded) is out of date.
The first step is to get your requirements. In the old days, you would go to the customer and get some information and put together a detailed specification that the customer would then sign off on. I prefer to speak to the customer to get an idea of what she wants and then put a basic site together so that early on in the process, she has an idea of what she is getting. Of course one of the advantages of drupal is that this is easily changed.
Next step is to set up your offline web site. To do this I use WAMP (Windows, Apache, MySQL and PHP). It turns out that my version is way out of date and when I uploaded and installed the new version over the old one, it didn't work. Major problem. I simply removed the previous version and changed the name of the Wamp folder to wampold and started from scratch.
Once installed, you can check two things. going to local host in your browser and coming up with the home page proves that you have connected to the server. Next you need to get PHPmyAdmin going. In my case I got a '2002' error telling me that I had been rejected:
#2002 - No connection could be made because the target machine actively refused it.
While the solution could be skype (try stopping it), this is the best answer I found and the one that worked for me:
left click wampmanager icon -> Apache -> httpd.conf
this will launch notpad to edit the Apache config file
Look for 'Listen' and change it to 'Listen 0.0.0.0:80'
reboot the software
Found the answer at this site:
http://forum.wampserver.com/read.php?2,110318
So finally having got the server going, go to PHPmyadmin and open a new empty database (with the name of your new site) and set up an admin user with a password..
Now you download the latest version of Drupal, make directory under wamp/www with the name of you new site and unzip drupal files (not the file name) into this site.
Go to your browser and type localhost/[new site name] and follow the installation instructions.
XAMPP
XAMPP is similar to WAMP in that it is a server that you set up on a Windows machine. I found that it was less intuitive, but more likely to work. I tried to get WAMP working again recently and failed.
Like WAMP, you simply download it and run it. Unlike WAMP, you have to start the various part manually. The two that are important are Apache and MySQL. PHP is also included but not in the control panel (which is a little irritating, but not a train smash). Once again, in order to set it up properly, I had to change the Apache port (using the config button) to 2375 (recommended) instead of port 80. The down side of this is that you have to go to localhost:2375 to find the main page of the server and localhost:2375/yourwebsite to get to your web site.
If you are using Drupal, there is one other trick that I only learned much later (which I couldn't edit my content types in Drupal) and this is probably applicable to WAMP as well.
- Open my.ini (this is the config file for MYSQL)
- Change max_allowed_packet from 1M to at least 5M (or increase it until the irritating error (PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone) has gone away
- When you install Drupal, first go to localhost:2375/PhpMyAdmin and add a database (name). You log in with the password that you set up for MySql.
- When installing Drupal, don't use the advanced tab and make settings there.
- The easiest way is to use the same username and password above.
Saturday, August 11, 2012
SQL 4111 error
I got a message from one of my users that he was unable to get into his site. Finger problems?? So I tried the site. Basically I got an SQL Server 4111 error with a whole page full of code. Ever heard of it? Neither had I so I tried googling with no real joy. There were a couple of hints like 'you've exceeded your quota'.
The interesting thing was that it wasn't just one site on the server that was having problems - most of the Drupal sites were. With some of the sites, I could not even log in and with others once logged in, I couldn't get to the config menu without an error.
I thought for the record I should detail how the problem appears to have been sorted but giving no guarantee that it wasn't going to happen again. The next step was to actually read the blurb that came with the error report and there was the solution. Errors were something like 'dr_cache full'. Not being totally knowledgeable about Drupal, but knowing that cache is something that is stored to save time getting it from somewhere else. The standard solution to a full cache is to clear it which should be possible through the config menu, but of course I was unable to get to the config menu.
The solution was to go to the server control console and fire up phpadmin. From there you can get to the relevant database which of course lists all of the tables in that database. The next step is to go through all the db_cache tables (dr_cachefield etc) and delete everything in them. Don't delete the actual table. I found that there were a couple of others that were also causing problems - namely the db_watchdog and the db_queue.
Each of these had data in the format BLOB (I thought this may be some wierd person trying to attack my database but no, it turns out that BLOB stands for a Binary Large OBject that can hold varying amounts of data - you learn something new every day!).
Once you've deleted the caches, you go back to your web site (suggest that you keep phpadmin open) and try again. It worked for me but not on the first try. What did happen was that the size of the error message got smaller so I was eventually able to delete cache contents until there were no more messages. First thing I did after that was to clear the cache (not sure if that helped) and to update all my modules.
Hope this helps someone. Let me know if it does!
The interesting thing was that it wasn't just one site on the server that was having problems - most of the Drupal sites were. With some of the sites, I could not even log in and with others once logged in, I couldn't get to the config menu without an error.
I thought for the record I should detail how the problem appears to have been sorted but giving no guarantee that it wasn't going to happen again. The next step was to actually read the blurb that came with the error report and there was the solution. Errors were something like 'dr_cache full'. Not being totally knowledgeable about Drupal, but knowing that cache is something that is stored to save time getting it from somewhere else. The standard solution to a full cache is to clear it which should be possible through the config menu, but of course I was unable to get to the config menu.
The solution was to go to the server control console and fire up phpadmin. From there you can get to the relevant database which of course lists all of the tables in that database. The next step is to go through all the db_cache tables (dr_cachefield etc) and delete everything in them. Don't delete the actual table. I found that there were a couple of others that were also causing problems - namely the db_watchdog and the db_queue.
Each of these had data in the format BLOB (I thought this may be some wierd person trying to attack my database but no, it turns out that BLOB stands for a Binary Large OBject that can hold varying amounts of data - you learn something new every day!).
Once you've deleted the caches, you go back to your web site (suggest that you keep phpadmin open) and try again. It worked for me but not on the first try. What did happen was that the size of the error message got smaller so I was eventually able to delete cache contents until there were no more messages. First thing I did after that was to clear the cache (not sure if that helped) and to update all my modules.
Hope this helps someone. Let me know if it does!
Wednesday, July 11, 2012
Forms
There are a couple of options when it comes to adding forms to Drupal 7. One is called Multiple forms which which is an API that allows you to put multiple forms into one.
Another is Webform which is a fairly sophisticated option. This one allows you to set up a form in such a way that the inputs are not all one below the other. I tried using this for one of my projects but found that the main problem with is was that you are not easily able to print out the form in such a way that it can be read. The module seems to offer only one font size which is too small for a user to complete and submit a paper copy. On the up side, it sends an e-mail to the person who filled in the form and to any other address you ask it to.
The problem was such that I eventually had to resort to a PDF type form which wasn't available in a Drupal module (worth looking at - its called PDF fill and you can set up PDF forms that users can complete and print on line - and of course a lot cheaper than the Adobe alternative!). Price is $19.99.
More recently on my Marlinspike Guest Lodge site, I made use of another module called qforms . This is a great module if you need to put something together quickly that you can use immediately. It offers the basic forms requirements and if you use qforms extra (which at the time I tried it still had a few problems), you can get a few more forms components.
The possible down side of qforms is that the forms are all stored online and you need to go online to see the responses. For the guest house site this is actually a good thing as you have a record of your responses easily available.
I recently had someone spamming the form and wanted to put captcha onto it. If you haven't met the captcha module - even though the current version for DR7 is still in Beta 2, my experience is that it works very well. A few points though:
Remember that if you are Admin and you have set the system not to ask you for Captcha input, you need to log out to test it.
If you want to use it with qforms, you need to add an extra option to captcha to allow you to do this. You need to go to the configuration page and choose captcha and then add the form ID at the bottom of the list. The easiest way is to look at the source of your form and take the ID (which has dashes - something like 'qforms-submit-form' and to use this with underscores 'qform_submit_form'. Its as easy as that. You can see it in action on the Marlinspike Guest Lodge Contact form where I've included a detailed contact form as well as a standard contact form (in case the visitor just has a simple enquiry.
Another is Webform which is a fairly sophisticated option. This one allows you to set up a form in such a way that the inputs are not all one below the other. I tried using this for one of my projects but found that the main problem with is was that you are not easily able to print out the form in such a way that it can be read. The module seems to offer only one font size which is too small for a user to complete and submit a paper copy. On the up side, it sends an e-mail to the person who filled in the form and to any other address you ask it to.
The problem was such that I eventually had to resort to a PDF type form which wasn't available in a Drupal module (worth looking at - its called PDF fill and you can set up PDF forms that users can complete and print on line - and of course a lot cheaper than the Adobe alternative!). Price is $19.99.
More recently on my Marlinspike Guest Lodge site, I made use of another module called qforms . This is a great module if you need to put something together quickly that you can use immediately. It offers the basic forms requirements and if you use qforms extra (which at the time I tried it still had a few problems), you can get a few more forms components.
The possible down side of qforms is that the forms are all stored online and you need to go online to see the responses. For the guest house site this is actually a good thing as you have a record of your responses easily available.
I recently had someone spamming the form and wanted to put captcha onto it. If you haven't met the captcha module - even though the current version for DR7 is still in Beta 2, my experience is that it works very well. A few points though:
Remember that if you are Admin and you have set the system not to ask you for Captcha input, you need to log out to test it.
If you want to use it with qforms, you need to add an extra option to captcha to allow you to do this. You need to go to the configuration page and choose captcha and then add the form ID at the bottom of the list. The easiest way is to look at the source of your form and take the ID (which has dashes - something like 'qforms-submit-form' and to use this with underscores 'qform_submit_form'. Its as easy as that. You can see it in action on the Marlinspike Guest Lodge Contact form where I've included a detailed contact form as well as a standard contact form (in case the visitor just has a simple enquiry.
Saturday, June 23, 2012
Tricks with Panels
22/6/2012
I'm using Panels 7.x-3.2 and Drupal 7.14. In the process of trying to get the slideshow to work I came across a few issues with Panels that I need to remember for next time (if I have the sense to check the blog first before spending a day trying to find solutions - as I did today with slideshow).
1. Panels is great. You can set up a node, a page, a block (mini-panel) and have a tabular css layout to get what you want. Don't panic, however when you try to modify this layout (that is the layout of the panel blocks, you suddenly get a major error. To avoid this happening (assuming you want to make up your own set of panels instead of using the standard ones) you first need to set up a custom layout.
The advantage of this is that if you have a number of layouts and you want to change them all at once - you just have to change the one. More importantly you should not get that pesky error that you get when you try to modify it on the fly.
2. There's a problem when you want to have an empty panel (well I had this problem anyway). I wanted my slide show in the middle of the page with areas for other content on either side. Solution is to make a blank node and put it into the panel. New problem - its the old 'node title' problem. Something about Drupal is that they don't give you an easy way to hide your node title - you have to do it in the .tpl file. The easiest solution is to just comment out the line that prints the title - you do it in the PANEL.tpl file if the (blanc node) is in a panel. Remember to use the basic node and not the article otherwise you will have author info that you can't get rid of!!)
3. You've set up a beautiful sliding show but damn me if the thing is left justified. You guessed it - there seems to be no easy way to centre (or is it center) anything in Drupal - you've got to go to the css file and add:
.slidecenter{
width: 500px;
margin-left: auto;
margin-right: auto;
}
then you go to the mini-panel that you've set up for the slider under panels and ..... oh dear there doesn't seem to be any way of editing it. For some reason when you simply click on min-panels that option doesn't come up. The simple solution is to click onto 'content' and voila you can edit again (took a while to get to that as well!). Anyway, when you go to content, you click on the panel that has the slider in it and choose css. Then you add the css class (in my case 'slidecenter' and the image should now centre.
4. Returning to panels (2 years later), I had to edit the panel format - this is actually for a newsletter that I am doing. Its a long story, but this is the best way to render the content of the newsletter - there'll be a dedicated section of this blog on that soon. When I tried to change the layout of the panel, I go a mysterious error from 'my site'. "you are not authorised to access this page'
First step was to check my admin to see that all the boxes are ticked - they are (well there were a few that weren't but they had nothing to do with panels). Next step (of course) was google. Eventually - lurking at the bottom of a response from the maker - was yes, there is a problem - but I never expected people to want to do things this way! Basically the error comes up if you edit a panel layout directly from 'edit content'. The solution turns out to be simple - go edit, go straight to 'panel content', go to layout editor. If you go to 'panel layout' you'll probably get the error.
The maker of panels is clearly in no rush to sort this one out as its been around for 2 years!
Here's the link to the initial report : https://www.drupal.org/node/1798846
I'm using Panels 7.x-3.2 and Drupal 7.14. In the process of trying to get the slideshow to work I came across a few issues with Panels that I need to remember for next time (if I have the sense to check the blog first before spending a day trying to find solutions - as I did today with slideshow).
1. Panels is great. You can set up a node, a page, a block (mini-panel) and have a tabular css layout to get what you want. Don't panic, however when you try to modify this layout (that is the layout of the panel blocks, you suddenly get a major error. To avoid this happening (assuming you want to make up your own set of panels instead of using the standard ones) you first need to set up a custom layout.
The advantage of this is that if you have a number of layouts and you want to change them all at once - you just have to change the one. More importantly you should not get that pesky error that you get when you try to modify it on the fly.
2. There's a problem when you want to have an empty panel (well I had this problem anyway). I wanted my slide show in the middle of the page with areas for other content on either side. Solution is to make a blank node and put it into the panel. New problem - its the old 'node title' problem. Something about Drupal is that they don't give you an easy way to hide your node title - you have to do it in the .tpl file. The easiest solution is to just comment out the line that prints the title - you do it in the PANEL.tpl file if the (blanc node) is in a panel. Remember to use the basic node and not the article otherwise you will have author info that you can't get rid of!!)
3. You've set up a beautiful sliding show but damn me if the thing is left justified. You guessed it - there seems to be no easy way to centre (or is it center) anything in Drupal - you've got to go to the css file and add:
.slidecenter{
width: 500px;
margin-left: auto;
margin-right: auto;
}
then you go to the mini-panel that you've set up for the slider under panels and ..... oh dear there doesn't seem to be any way of editing it. For some reason when you simply click on min-panels that option doesn't come up. The simple solution is to click onto 'content' and voila you can edit again (took a while to get to that as well!). Anyway, when you go to content, you click on the panel that has the slider in it and choose css. Then you add the css class (in my case 'slidecenter' and the image should now centre.
4. Returning to panels (2 years later), I had to edit the panel format - this is actually for a newsletter that I am doing. Its a long story, but this is the best way to render the content of the newsletter - there'll be a dedicated section of this blog on that soon. When I tried to change the layout of the panel, I go a mysterious error from 'my site'. "you are not authorised to access this page'
First step was to check my admin to see that all the boxes are ticked - they are (well there were a few that weren't but they had nothing to do with panels). Next step (of course) was google. Eventually - lurking at the bottom of a response from the maker - was yes, there is a problem - but I never expected people to want to do things this way! Basically the error comes up if you edit a panel layout directly from 'edit content'. The solution turns out to be simple - go edit, go straight to 'panel content', go to layout editor. If you go to 'panel layout' you'll probably get the error.
The maker of panels is clearly in no rush to sort this one out as its been around for 2 years!
Here's the link to the initial report : https://www.drupal.org/node/1798846
Thursday, June 21, 2012
Views SlideShow
10/5/12
Putting together an e-commerce type site which will include the sale of computer equipment and I need to have a front page block which will display the latest specials. The prior 'Slideshow' module looked like a suitable option as it simply provides a slideshow of the images in exisiting nodes, but this is only available to DR6 and is no longer supported.
Views Slideshow looks a lot more complicated, but I have decided to give it a go.
Installed Views Slideshow and Views Slideshow Cycle
Instructions found at http://drupal.org/node/903244
I see that all isn't as easy as it looks - its one of these modules that needs you to download something else from somewhere else. In this case I downloaded a file called malsup-cycle and then re-name the file jquery.cycle.all.js to jquery.cycle.all.min.js and put this in a newly created directory under libraries called jquery.cycle. Actually I SHOULD have found jquery.cycle.all.latest.js and downloaded an renamed that one. Nothing is simple in life.
Still nothing when I look under the front page of views (but see below).
Looked at tutorial - seems to require a module called Link Field. Cleared Views Cache - no change.
Another thing I discovered was that 'slideshow' does NOT appear on the Views page. You have to create a new view and it becomes one of the display formats. This is really irritating because there doesn't seem to be anything that mentions this on the slideshow page - in fact it says that it should be there.
Following the tutorial worked well. Take a look a the results at http://www.innomark.co.za.
10/5/12
Putting together an e-commerce type site which will include the sale of computer equipment and I need to have a front page block which will display the latest specials. The prior 'Slideshow' module looked like a suitable option as it simply provides a slideshow of the images in exisiting nodes, but this is only available to DR6 and is no longer supported.
Views Slideshow looks a lot more complicated, but I have decided to give it a go.
Installed Views Slideshow and Views Slideshow Cycle
Instructions found at http://drupal.org/node/903244
I see that all isn't as easy as it looks - its one of these modules that needs you to download something else from somewhere else. In this case I downloaded a file called malsup-cycle and then re-name the file jquery.cycle.all.js to jquery.cycle.all.min.js and put this in a newly created directory under libraries called jquery.cycle. Actually I SHOULD have found jquery.cycle.all.latest.js and downloaded an renamed that one. Nothing is simple in life.
Still nothing when I look under the front page of views (but see below).
Looked at tutorial - seems to require a module called Link Field. Cleared Views Cache - no change.
Another thing I discovered was that 'slideshow' does NOT appear on the Views page. You have to create a new view and it becomes one of the display formats. This is really irritating because there doesn't seem to be anything that mentions this on the slideshow page - in fact it says that it should be there.
Following the tutorial worked well. Take a look a the results at http://www.innomark.co.za.
Subscribe to:
Comments (Atom)