[Radiant] how to debug mailer extension?
Hi, Thanks to the great help from the list, I've got my mailer extension set up. I made a contact form following the example, but it did not go through -- the form takes a long time to get submitted and I can't received the message on the other end. I tested all the smtp settings using my own email client and things worked fine. I wonder if there is any way to find out what went wrong. The server runs Phussion Passenger. Would there be any error logs? Thanks. ming ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] how to debug mailer extension?
Ming- I have a section on troubleshooting Mailer on this blog post: http://www.banane.com/2009/10/27/radiant-mailer-extension-installation-basics/ On Tue, Feb 2, 2010 at 8:26 AM, Ming Pan fallspin...@gmail.com wrote: Hi, Thanks to the great help from the list, I've got my mailer extension set up. I made a contact form following the example, but it did not go through -- the form takes a long time to get submitted and I can't received the message on the other end. I tested all the smtp settings using my own email client and things worked fine. I wonder if there is any way to find out what went wrong. The server runs Phussion Passenger. Would there be any error logs? Thanks. ming ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] how to debug mailer extension?
Thanks Banane. I'm still struggling with it. My SMTP server requires SSL on port 465, and I put :tls = true and :port = 465 in the settings, but no luck yet. Could it be possible that it requires some kind of tls plugin but I don't have it? If so, how to tell whether I have it or how to install it? ming On Tue, Feb 2, 2010 at 12:33 PM, banane ban...@gmail.com wrote: Ming- I have a section on troubleshooting Mailer on this blog post: http://www.banane.com/2009/10/27/radiant-mailer-extension-installation-basics/ On Tue, Feb 2, 2010 at 8:26 AM, Ming Pan fallspin...@gmail.com wrote: Hi, Thanks to the great help from the list, I've got my mailer extension set up. I made a contact form following the example, but it did not go through -- the form takes a long time to get submitted and I can't received the message on the other end. I tested all the smtp settings using my own email client and things worked fine. I wonder if there is any way to find out what went wrong. The server runs Phussion Passenger. Would there be any error logs? Thanks. ming ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] how to debug mailer extension?
Ming, Make sure to check your log (production or development, whatever Rails environmnet you have setup.) Also, yes, you need a plugin if your'e doing TLS, and you clone it to your plugins directory. git://github.com/collectiveidea/action_mailer_optional_tls.git That's a good one. It's all in the blog post, btw. Anna ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] how to debug mailer extension?
I just had the action_mailer_optional_tls installed in my plugins
directory. The following is the only record I find about my submission
of a test message, and it seems no smtp request has ever been
initiated:
Processing MailController#create (for 68.36.169.117 at 2010-02-02
14:10:46) [POST]
Parameters: {page_id=19, action=create,
mailer={name=asdf, message=f asdfasdf ,
email=a...@zsdf.com}, controller=mail}
Completed in 158ms (View: 0, DB: 3) | 200 OK
[http://www.wangintlgroup.com/pages/19/mail]
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org
[Radiant] Redirecting /
For various reasons I'd like to have the Home on my site menu go to /home (and the About go to /about and so on.) Creating /home and the sections that go into it which get managed as child pages - for editing/organization reasons - isn't the problem. The problem is that people visit http://MyDomain.com which is really MyDomain.com/ or in radiant terms / and not http://MyDomain.com/home Now I know if this was my own site I could play around with Apache and redirect, if I knew enough about Apache's redirect and had access to it, which I don't, and its all messed up by use of Dreamhost's funny implementation of Passenger anyway. I know there's 'routes.rb' but will that survive upgrades? I suspect not. Any other suggestions? Is there something in Rails or Radiant that does this that I'm unaware of? -- Growth for the sake of growth is the ideology of the cancer cell. - Edward Abbey ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Designing the Radiant Way?
Daniel O'Connell said the following on 02/02/2010 08:18 PM: Hello to all, I'm still trying to get my head around designing a website with Radiant in mind. The biggest problem for me seems to be figuring out how to write the layout html so that Radiant knows where the content will go. For instance, with a multi-column layout how do you determine where the body or other page part will go in the layout so that it makes sense in Radiant. Could any of you seasoned veterans explain the process you use to design a website with Radiant in mind. How do you create a theme? Create 1, 2 or more column layout? I started to write this up but I rapidly found that explaining it was about 20-30 times as much work as doing it. Lets see it I can get it done quick. 1. Go to Andreas Viklund's site http://andreasviklund.com/ and download a FREE template. Get a zip file and unpack it. 2. Put .. The HTML a named template The CSS in public/stylesheet The images in /public/images 3. Go to the template. Go the head section Edit the reference to the stylesheet to match where you put the stylesheet. Go through the bodyto find references to images and edit them to match where you put the images. 4. Create the / page. Set its template to be named template you created in #1 5. Test by pointing your browser at the base of the site. It *should* look like Andreas' example. If it doesn't, then you've made a mistake in #2 and #3 6. Create some dummy content of you own in / 7. Go to the template and find out where in body the example content is. Leave all the menu stuff alone for now. Replace Andreas' wordage with r:content / 8. Test. You should now see your won content. 9. Gradually replace more of the basics in the template with your own material. I strongly suggest doing this: a) take the main menu stuff from the template and put it in a snippet called mainmenu and replace it in the template with r:snippet name=mainmenu / b) test You can do that with other chunks of stuff. With a bit of practice you can do that in less time than it took me to write this. Now, based on hard earned experience, I suggest your template has bits like this in it ... div id=sidebar r:content part=sidebar-hi inherit=true / r:content part=sidebar inherit=true / r:content part=sidebar-page / r:content part=sidebar-low inherit=true / /div !-- end sidebar -- div class=clearnbsp;/div You'll soon figure out what to do with the hi low and page-specific parts :-) You might also want to use this as your template's core div id=content r:unless_url matches=^/$ h1 class=headerstyler:title //h1 /r:unless_url r:content / !-- page main content -- p class=insidelink[ a href=#topBack to top/a ]/p r:if_content part=extended div id=extended r:content part=extended / /div !-- end extended -- p class=insidelink[ a href=#topBack to top/a ]/p /r:if_content r:if_content part=extended2 div id=extended2 r:content part=extended2 / /div !-- end extended2 -- p class=insidelink[ a href=#topBack to top/a ]/p /r:if_content /div !-- end div.content -- If you don't see it at first, trust me, you'll soon find out why :-) I've also found it useful to have this like in the head r:if_content part=head r:content part=head / /r:if_content I know that Radiant is only at 0.8.1 (stable) But there really needs to be better theming ability, and more documentation for those who struggle as I do with the programming end of things. I'm not happy with the idea of introducing theming the way WordPress or Joomla does into Radiant. Its too restrictive. If you just try converting the nine free examples that Andreas gives you'll find that they have awkward fits. I'm working on a site based on his '03' example. http://andreasviklund.com/templates/andreas03/ The top part has two extra bit, the logo where it says speed and accessibility and the caption where it says Presentation ... You need page-parts for those. You may -or may not- want them inherited. So Obviously the theme has to dictate what page parts you can or cannot have. If you develop with andreas01 http://andreasviklund.com/files/demo/andreas01/ and then move to Andreas03, you're in a mess - you've moved from two sidebars to one and you've got slots for two page parts that didn't exist before. What's the solution? Well, OK, 0-sidebar, 1-sidebar and 2-sidebar types of themes. Uh-oh! Someone isn't going to like that! Perhaps you need to use Joomla after all ... I would also love to see a Radiant CMS for dummies or other instruction geared for beginners offered for sale. I think the real problem with Radiant is that
Re: [Radiant] Designing the Radiant Way?
I've got a template that might be helpful for you: http://github.com/indexzero/radiant-scribbish-theme It uses several content parts as well as the if_content part= /. Hope that helps you! Charlie On Tue, Feb 2, 2010 at 9:41 PM, Anton Aylward anton.aylw...@rogers.comwrote: Daniel O'Connell said the following on 02/02/2010 08:18 PM: Hello to all, I'm still trying to get my head around designing a website with Radiant in mind. The biggest problem for me seems to be figuring out how to write the layout html so that Radiant knows where the content will go. For instance, with a multi-column layout how do you determine where the body or other page part will go in the layout so that it makes sense in Radiant. Could any of you seasoned veterans explain the process you use to design a website with Radiant in mind. How do you create a theme? Create 1, 2 or more column layout? I started to write this up but I rapidly found that explaining it was about 20-30 times as much work as doing it. Lets see it I can get it done quick. 1. Go to Andreas Viklund's site http://andreasviklund.com/ and download a FREE template. Get a zip file and unpack it. 2. Put .. The HTML a named template The CSS in public/stylesheet The images in /public/images 3. Go to the template. Go the head section Edit the reference to the stylesheet to match where you put the stylesheet. Go through the bodyto find references to images and edit them to match where you put the images. 4. Create the / page. Set its template to be named template you created in #1 5. Test by pointing your browser at the base of the site. It *should* look like Andreas' example. If it doesn't, then you've made a mistake in #2 and #3 6. Create some dummy content of you own in / 7. Go to the template and find out where in body the example content is. Leave all the menu stuff alone for now. Replace Andreas' wordage with r:content / 8. Test. You should now see your won content. 9. Gradually replace more of the basics in the template with your own material. I strongly suggest doing this: a) take the main menu stuff from the template and put it in a snippet called mainmenu and replace it in the template with r:snippet name=mainmenu / b) test You can do that with other chunks of stuff. With a bit of practice you can do that in less time than it took me to write this. Now, based on hard earned experience, I suggest your template has bits like this in it ... div id=sidebar r:content part=sidebar-hi inherit=true / r:content part=sidebar inherit=true / r:content part=sidebar-page / r:content part=sidebar-low inherit=true / /div !-- end sidebar -- div class=clearnbsp;/div You'll soon figure out what to do with the hi low and page-specific parts :-) You might also want to use this as your template's core div id=content r:unless_url matches=^/$ h1 class=headerstyler:title //h1 /r:unless_url r:content / !-- page main content -- p class=insidelink[ a href=#topBack to top/a ]/p r:if_content part=extended div id=extended r:content part=extended / /div !-- end extended -- p class=insidelink[ a href=#topBack to top/a ]/p /r:if_content r:if_content part=extended2 div id=extended2 r:content part=extended2 / /div !-- end extended2 -- p class=insidelink[ a href=#topBack to top/a ]/p /r:if_content /div !-- end div.content -- If you don't see it at first, trust me, you'll soon find out why :-) I've also found it useful to have this like in the head r:if_content part=head r:content part=head / /r:if_content I know that Radiant is only at 0.8.1 (stable) But there really needs to be better theming ability, and more documentation for those who struggle as I do with the programming end of things. I'm not happy with the idea of introducing theming the way WordPress or Joomla does into Radiant. Its too restrictive. If you just try converting the nine free examples that Andreas gives you'll find that they have awkward fits. I'm working on a site based on his '03' example. http://andreasviklund.com/templates/andreas03/ The top part has two extra bit, the logo where it says speed and accessibility and the caption where it says Presentation ... You need page-parts for those. You may -or may not- want them inherited. So Obviously the theme has to dictate what page parts you can or cannot have. If you develop with andreas01 http://andreasviklund.com/files/demo/andreas01/ and then move to Andreas03, you're in a mess - you've moved from two sidebars to one and you've got slots for two page parts that didn't exist before.
Re: [Radiant] Designing the Radiant Way?
I've built probably 20 sites in radiant and although each site has similar requirements, there are just as many differences. I usually have a default set of pages and CSS I create and I always use the nested_layouts extension by default. Usually Home pages are different than child pages so I give them a separate layout. If I need a two column layout, I make a separate, two column template using XHTML, CSS, and 960.gs columns for reference and stick in my Radius tags to make the content happen. I started out trying to use if_url, if_content part and other conditionals to figure out if the current page needed multiple columns or not, but I find it much simpler now to make a unique layout depending on what the page requires and just set the pages layout manually. The nested_layouts extension makes it much simpler to roll out new layouts as needed. I found out the gain in building a pristine layout that automatically adjusted to each page was not worth the time and effort and it was usually complicated and difficult to change anyway. Just about every time, the project I'm working on needs something unique (and rightly so) so I don't bother building a catch-all layout. I just build it as it comes. I'm sure if I got obsessed with building a theme it would get hacked to pieces in the end anyway when it was put into production. I really like the Joomla and Wordpress contrasting going on because I love how Radiant topples those CMS's design philosophies. Every time I work in Wordpress or Joomla I get frustrated because I don't have the freedom of Radius and Layouts. On Tue, Feb 2, 2010 at 9:46 PM, Charlie Robbins charlie.robb...@gmail.com wrote: I've got a template that might be helpful for you: http://github.com/indexzero/radiant-scribbish-theme It uses several content parts as well as the if_content part= /. Hope that helps you! Charlie On Tue, Feb 2, 2010 at 9:41 PM, Anton Aylward anton.aylw...@rogers.comwrote: Daniel O'Connell said the following on 02/02/2010 08:18 PM: Hello to all, I'm still trying to get my head around designing a website with Radiant in mind. The biggest problem for me seems to be figuring out how to write the layout html so that Radiant knows where the content will go. For instance, with a multi-column layout how do you determine where the body or other page part will go in the layout so that it makes sense in Radiant. Could any of you seasoned veterans explain the process you use to design a website with Radiant in mind. How do you create a theme? Create 1, 2 or more column layout? I started to write this up but I rapidly found that explaining it was about 20-30 times as much work as doing it. Lets see it I can get it done quick. 1. Go to Andreas Viklund's site http://andreasviklund.com/ and download a FREE template. Get a zip file and unpack it. 2. Put .. The HTML a named template The CSS in public/stylesheet The images in /public/images 3. Go to the template. Go the head section Edit the reference to the stylesheet to match where you put the stylesheet. Go through the bodyto find references to images and edit them to match where you put the images. 4. Create the / page. Set its template to be named template you created in #1 5. Test by pointing your browser at the base of the site. It *should* look like Andreas' example. If it doesn't, then you've made a mistake in #2 and #3 6. Create some dummy content of you own in / 7. Go to the template and find out where in body the example content is. Leave all the menu stuff alone for now. Replace Andreas' wordage with r:content / 8. Test. You should now see your won content. 9. Gradually replace more of the basics in the template with your own material. I strongly suggest doing this: a) take the main menu stuff from the template and put it in a snippet called mainmenu and replace it in the template with r:snippet name=mainmenu / b) test You can do that with other chunks of stuff. With a bit of practice you can do that in less time than it took me to write this. Now, based on hard earned experience, I suggest your template has bits like this in it ... div id=sidebar r:content part=sidebar-hi inherit=true / r:content part=sidebar inherit=true / r:content part=sidebar-page / r:content part=sidebar-low inherit=true / /div !-- end sidebar -- div class=clearnbsp;/div You'll soon figure out what to do with the hi low and page-specific parts :-) You might also want to use this as your template's core div id=content r:unless_url matches=^/$ h1 class=headerstyler:title //h1 /r:unless_url r:content / !-- page main content -- p class=insidelink[ a href=#topBack to top/a ]/p r:if_content part=extended div id=extended
Re: [Radiant] Redirecting /
The quick-and-dirty way is to add a meta tag to the HTML of your root page: meta http-equiv=Refresh content=0; url=/home / Or you could use an extension like Vapor that lets you create arbitrary redirects (I like Vapor a lot ;) Sean On 2/2/10 7:09 PM, Anton Aylward wrote: For various reasons I'd like to have the Home on my site menu go to /home (and the About go to /about and so on.) Creating /home and the sections that go into it which get managed as child pages - for editing/organization reasons - isn't the problem. The problem is that people visit http://MyDomain.com which is really MyDomain.com/ or in radiant terms / and not http://MyDomain.com/home Now I know if this was my own site I could play around with Apache and redirect, if I knew enough about Apache's redirect and had access to it, which I don't, and its all messed up by use of Dreamhost's funny implementation of Passenger anyway. I know there's 'routes.rb' but will that survive upgrades? I suspect not. Any other suggestions? Is there something in Rails or Radiant that does this that I'm unaware of? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
