[Radiant] autosave for content articles

[Ben Still]

Hi there,
one of our content editors has been having problems when working with 
long pages. The admin UI times out, and when she tries to save she finds 
she is logged out and loses all changes.


We are extending the timeout, but were also thinking about creating an 
autosave feature (for existing content), as it might prove handy.


Has anyone implemented anything like this already? If not, does anyone 
have any feature suggestions? (keeping in mind we'd like to keep this 
super simple and avoid The Bloat)


thanks

Ben


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] autosave for content article

[Ben Still]

Hi everyone,
we've found the cause of the timeouts we were having when leaving a page 
open for too long. It turned out to be a memcache setting in production.rb


config.action_controller.session_store = :mem_cache_store
ActionController::Base.session_options[:expires] = 1800

I was going to add this in to the Troubleshooting section of the Reboot, 
but wasn't quite sure as it isn't actually Radiant issue as such. This 
setting isn't in production.rb by default -it was something that we had 
 added in at some point.


regards

Ben


Josh French wrote:
There is a session timeout, but it defaults to two weeks (see 
lib/radiant/setup.rb) -- either that's a REALLY long article, or 
something else is afoot. Ben, what version of Radiant are you using? The 
default session store was switched to cookies at the same time the 
remember-me functionality was introduced; my first guess would be some 
unforeseen corner case involving cookie handling.


j

On Aug 13, 2008, at 8:50 AM, [EMAIL PROTECTED] wrote:


With the latest Radiant, you also have the "Remember me" functionality
that can be used to keep her logged in.  I don't recall there being a
default session timeout, but I may be mistaken.


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant



--
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] autosave for content article

[Ben Still]

Hi Mohit,
ok, that makes sense. I'd be happy to write something around the 
memcache issue, why use it, as it might be something that others might 
find useful. If you have any suggestions on location in the 
documentation, let me know.


We started using it when we built a site for Earthhour 2008 
http://www.earthhour.org in Radiant, and it started getting significant 
traffic - peaking at ~3M a day.


We used memcahce to improve Rails session handling, and also piped the 
Radiant cache into memcache to serve pages directly from RAM instead of 
disk.


regards

Ben

Mohit Sindhwani wrote:

Ben Still wrote:

Hi everyone,
we've found the cause of the timeouts we were having when leaving a 
page open for too long. It turned out to be a memcache setting in 
production.rb


config.action_controller.session_store = :mem_cache_store
ActionController::Base.session_options[:expires] = 1800

I was going to add this in to the Troubleshooting section of the 
Reboot, but wasn't quite sure as it isn't actually Radiant issue as 
such. This setting isn't in production.rb by default -it was something 
that we had  added in at some point.


Ben, as regards whether this should go in to the Summer Reboot, you're 
right, it is a bit specific to the way that you were doing things.  My 
guess is that it won't make sense till the reason why you made the 
change is explained.  I see 2 ways:

* It doesn't seem to belong in Troubleshooting - so just let it be
* If you ever get the chance to explain why use mem_cache and set the 
expiry settings, it might make sense as a small article of its own.


But, it seems like it currently targets a very small group of people.  
At some point, if we have something about sessions, as used in Radiant, 
it would be good to have this.


Cheers,
Mohit.
8/19/2008 | 9:38 AM.





--



___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Re: google analytics as extension

[Ben Still]

Hi Jasper,
just in case you or anyone else on the list is on a fruitless search to 
also implement event tracking as part of your work with ga.js, it would 
*appear* that this is still in beta. The event stuff is well documented, 
but I had to dig around to find out why I wasn't seeing anything 
appearing in the GA reports. You need to apply to get on the Trusted 
Tester program to get this switched on for your account

http://code.google.com/apis/analytics/docs/trustedTester.html

Event docs are here (basically same as pages but with additional 
parameters, which you might find useful)

http://code.google.com/apis/analytics/docs/eventTrackerGuide.html

regards

Ben

Adam van den Hoven wrote:

Jasper,

I believe that Marcus' point was that instead of hard coding it into the 
HTML, that you write some JavaScript code to do it for you. Something 
like this should be more than fast enough for your needs:


(function (){
  //Always isolate your JavaScript from the global scope
  var links = document.getElementsByTagName("a"),
  this_host = window.location.host;
  for (var i = links.length - 1, lnk; i >= 0; i--){
 lnk = links[i];
 if (lnk.host !== this_host) {
lnk.onClick = "pageTracker._trackPageview('outbound/" + lnk.href 
+ "');"

};
  };
})();

I haven't tested it but it should work, more or less correctly. You 
could use a library to set the event, if you like, but looping through 
the anchors this way is the fastest possible way to do it.


Adam

On 30-Sep-08, at 9:59 PM, Jasper Kooij wrote:


Hi Marcus,

How is the above ga tracking different from the new ga.js? That's the
one I'm using on my wordpress where I can specify by means of a pluging
van joost de valk.

Here is the screenshot of the settings in wordpress for example using
the ga.js to tag:

http://screencast.com/t/l3orhxHo3wq

I'm not trying to reinvent the wheel, just measuring on a website what's
working and what's not.

the outbound tag in
pageTracker._trackPageview('outbound/http://davidseah.com/blog/the-printable-ceo-series/') 


and simply be replaced by a preset or specified one. I've checked the
analytics and the tagging works well that way.

The only thing is that the JS code needs to be loaded before the
pageTracker is being called.

So I'm going through the tutorial in creating an extension at the summer
reboot http://wiki.radiantcms.org/Creating_an_extension_I


Jasper
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant



--



Ben Still  |  Red Ant  |  office +612 9267 8300 ext 208  | mobile 0425 
294 271

___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Accidently removed the body of contest2.radiantcms.org/

[Ben Still]

-1 on the rich text editor from over here

Joe Van Dyk wrote:


Other things that we think most people would want by default:

- some sort of rich text editor
- asset manager better integrated

It would be great to have these as extensions, but installed by
default.  Having an officially "blessed" extension is important for
quality, in our opinion.

One of the things I love about Radiant is that it is "no fluff". It goes 
down a different path to say Drupal, where you get the kitchen sink by 
default. Certainly- I think blessed extensions are a good idea, and we 
should include these in the manual eg: How to make a blog. If you want 
to install that extension, it is your option.


Having a lean & mean/no fluff system by default means that people 
evaluating don't get confused - say thinking X is better than Radiant 
just because the wysiwyg editor looked nicer.


regards

Ben
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Content Internationalization

[Ben Still]

Hi Doug,
We've done a number of sites now that need to cover two or three 
markets. I thought it might be useful to share this as it's something 
we've come up against a few times.


I realise that you're asking about internationalisation as in having an 
identical page that can render in different languages. In sites we've 
worked on, this often also means different prices and product fact 
sheets etc. The easiest thing from a development perspective is having 
one site, then make it smart to render out the different flavour 
depending on URL or cookie.


We've run into two issues on that. First is the customer wanting 
slightly different behaviour or structure on one but not the others. A 
few changes are manageable, but as you can imagine this can get out of 
control and become a bit of a nightmare of localisation hacks.


The second issue is SEO and localisation. Apparently physical location 
is a big deal. If you want to rank well with Japanese customers, use a 
Japanese TLD and host out of a Japanese rather than say a US datacentre. 
I realise in your example the Spanish version might well be for Spanish 
rather than English speakers in the US- this example is for different 
geographic markets.


So, faced with those two issues, we typically make several different 
sites with one code repository. We've found this much easier in the long 
run. Capistrano manages the updates to each site so code remains the 
same, but the content is separate. A bit of a drag in that the content 
editor has to go to different /admins, but allows for flexible changes 
to structure and content, as well as addressing the SEO issue.


Anyway- hope that helps someone at some stage

regards

Ben

Doug Bryant wrote:
I'm currently looking at integrating radiant cms into our site.  One of 
the requirements we have coming down the pipeline soon is 
internationalization.


Is there a best practice anyone could suggest for internationalization 
of the content with Radiant?  I ran across a couple of posts from May 
2007 about doing this, but am checking because I don't know if this is 
still the suggested route.  Does the rails 2.3 feature of rendering 
internationalization snippets change any recommendations? (:render 
:partial => "foo" would render _foo.en.html or _foo.es.html depending on 
current locale)


http://www.mail-archive.com/radi...@lists.radiantcms.org/msg04509.html
http://www.mail-archive.com/radi...@lists.radiantcms.org/msg04535.html


What I envision is splitting out the content part of our app and 
integrating it into Radiant.  We have someone who would then be able to 
translate & maintain the spanish version of the website.  Content does 
not presently change too frequently, but would it if didn't require a 
complete application redeploy just to update a some portion of the content.


Any suggestions?

All feedback is greatly appreciated.

Doug

===
Doug Bryant
doug.bry...@milemeter.com



___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant



--



Ben Still  |  Red Ant  |  office +612 9267 8300 ext 208  | mobile 0425 
294 271

___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant