Autometically create editions as a new day starts
Mon, 05/04/2010 - 02:46
I got a lot of questions!
Well this will be a very hard work to create all the editions everyday and I have several top menus, each are tied upto their channel. Once an user submits a story with few channels selected, it should be able publish on the current date edition and under the menu/channel Is there a configuration to do that, or may be a sql query with all the channel names, current date passed into it.----------------
Installed the nodewords/meta tag. what I see the meta tag fields comes down submit button in the channel edit page so you can't add meta tags for a channel. Learning it more.. I guess it could done through a new edition for that channel but that means you got put meta tags everyday as a new edition is created - is there any other way to it.
-----------------
Is it Ok to use AuthCache
---------------
How to remove the rich text editor in comments.
Tue, 06/04/2010 - 13:15
#2
...
Hi,
You're right ... it is a lot of questions :)
I will try to answer them all in turn, but if I miss any of them, or if I say anything that is not clear, please ask again.
----------------
> Once an user submits a story with few channels selected, it
> should be able publish on the current date edition
There is one way I can think of to do this (using Channel Sub-blocks), although whether it exactly meets your needs is uncertain. It's also a bit complicated too, so this 'feature request' may be worth reviewing for potential re-implementation.
Anyway, I digress ... Using Channel sub-blocks to achieve this is as follows ...
Find and view an edition node that you want this behaviour for, then click on the Edit tab to edit the edition node.
Enable Composite Layout for this node by expanding the Composite layout fieldset and selecting a layout. Then click Save at the bottom of the page. This will enable composite layout (and all your content will seem to magically disappear but please don't worry - the content is still there - it's just hidden away).
You will have a whole bunch of local tasks appear. Click on the Channel sub-blocks tab, find a channel(s) of interest and tick the checkbox(es) next to it and click Save.
Then visit the Zones tab. Here is where you control the layout of items into zones. Find your 'Channel sub-block: ...' item in the Disabled section and move it to a zone. Then click Save zones. This will make your channel sub-block visible.
Next (whilst still on the Zones page) ... there is a configure link in the Additional settings column. Click on that to configure your channel sub-block. You can ask it to display the last X stories of a channel and hopefully this does what you want.
However ... looking back at what I wrote ... you might get lost following it because Composite Layout is another piece of functionality you need to be familiar with first. Maybe try follow as best as you can, play around with Composite Layout first and once you've used it a bit, come back and re-ask your question in light of what you know?
----------------
You can add keywords as meta tags when editing a channel, but the meta tags won't show up in edition nodes although they will show up for stories assigned to that channel. The reason is subtle and before attempt to go into it in detail ... I want to pose this question to you...
Are you using meta tags for a specific reason such as to gain more hits from Google? If so, then I'd suggest that meta tags don't really help. In recent times, meta tags have been abused so much by websites that Google (and most other search engines) just ignore them. You might want to do more research into this.
----------------
> Is it Ok to use AuthCache
Yes. I don't see why that wouldn't work.
----------------
> How to remove the rich text editor in comments.
Visit .../admin/settings/pp_ed on your site, expand the Editor visibility settings fieldset, untick Use the visual editor for comments and click Save configuration.
----------------
> How to change the title in contributers page
You need to change the Title setting for the General view display, not the Defaults display.
Wed, 07/04/2010 - 23:06
#3
Thank you for the reply..
Thank you for the reply.. unless you had that kind of patience you won't been able to develop this....
I am on 7th round of reading your reply :) .. ( I did able to do some changes as in the zones...its long way to get into it fully...)
The worm of questions bump me again
How to restrict an user from editing it when a 'ready for review' story was approved and published on the site.
Thu, 08/04/2010 - 03:46
#4
And I found a little
And I found a little error.
On the rss feed's xml
it shows like -
<link>http://mydomain.com/admin/content/stories/8</link>Which is not a public url, so when the crawlers are trying to access it, it gives 403 err.
Thu, 08/04/2010 - 11:46
#5
...
> How to restrict an user from editing it when a 'ready for review' story was approved and published on the site.
Okay, this gets a bit hairy because the page you need to visit has a lot of configuration options on it ...
Visit http://dev.drume.dev/admin/build/workflow/edit/1 (also reached via Administer // Site Building // Workflow and then Edit the Workflow).
Near the bottom of this page, look for the nested fieldset Access control -> Ready for review and then look in the column Roles who can edit posts in this state:. Untick the checkbox which says author (or fiddle around with it as you like).
Then click Save.
> On the rss feed's xml
Can you tell me the url of this xml feed? It might be an admin-only feed so the public wouldn't see the link in the first place.
Thu, 08/04/2010 - 13:05
#6
Just got it quick from the
Just got it quick from the demo
See the xml source - http://demo.prosepoint.org/channel/1/stories/0/feed
<link>http://demo.prosepoint.org/admin/content/stories/1</link>Try to access it publicly - http://demo.prosepoint.org/admin/content/stories/1
Feed bots are finding this as this feed's url.
Fri, 09/04/2010 - 10:13
#7
...
Hi,
Okay, I see the symptom. The rss is based off the wrong url - although the content is correct. Will get this fixed. Thanks for pointing it out.
Fri, 09/04/2010 - 10:40
#8
Channel xmlrss feeds based off incorrect admin/content/stories/*
A fix has been created for this and will be incorporated into the next ProsePoint release.
If any other readers read this and want to hand patch their systems to incorporate this fix, let me know.
Thank you.
Mon, 12/04/2010 - 01:25
#9
Could you paste the rss patch
Could you paste the rss patch please.. though the site doesn't have much now but I am just being paranoid when googs and others regularly trying to access them :)
Also 1. it would be nice to have the rss feed url like - domain/channel name/rss, I checked some 'category' urls in the rss xml, it shows a taxonomy path, it should be the channel path rewriten by pathauto - basically the page url the category belongs to. 2. the story author name should be firstname lastname (if profile installed) not his/her username.
Meta tags - Yes. I am not stuffing up things to get some 'seo', just for some channel titles it would be nice to add little more than the menu name.. While using sub-zones in editions as you've described above, it doesn't put 'Page title' value or meta desc. etc. on the channel page.
..little shy to share the site right now, but :)
Mon, 12/04/2010 - 14:07
#10
...
Hi,
Instructions for the rss xml 'patch':
Edit the file .../profiles/prosepoint/modules/prosepoint/views/story_view.view on your site. Look around line 655 for the two lines which say:
$handler->override_option('title', '');
$handler->override_option('style_plugin', 'rss');and replace them with:
$handler->override_option('title', '');
$handler->override_option('link_display', 'page_3');
$handler->override_option('style_plugin', 'rss');In other words, insert the line $handler->override_option('link_display', 'page_3');
Do this as a copy-and-paste. Don't hand type it in.
Then clear your site's cache and check it has been fixed.
> Also 1. it would be nice to have the rss feed url like - domain/channel name/rss,
Can you try manually configure this by hand-creating some url aliases?
> 2. the story author name should be firstname lastname (if profile installed) not his/her username.
Hmmm ... there's no easy way to do this generically, since a site can have different profile fields being used for firstname and lastname. You might be able to get what you want with Views (if you are comfortable editing story_view through the Views UI), otherwise some custom code would easily do the trick - but in a site-specific way.
> Meta tags - Yes. I am not stuffing up things to get some 'seo', just for some
> channel titles it would be nice to add little more than the menu name..
Hmmm ... if it's a simple change, I can probably put it in. Can you please rephrase and clarify more exactly what you'd like? Maybe provide some example urls? There's still some ambiguity in your descriptions so far.
God.. how could I live with so many questions, here is another one
How to change the title in contributers page (view: sources_list), I went to edit view on view ui and put 'Editors' as title in 'default settings for this view'. but it still shows
ContributorsI was able to change the 'path' from /contributers to /editors by the path alias.