Prosepoint vs Drupal upgrade
Wed, 20/05/2009 - 11:10
I just upgraded Prosepoint and everything went fine.
I was wondering, however, about the difference in procedures. The Drupal upgrade suggest disabling contributed and customize modules first. Apparently that is not necessary when using Prosepoint to upgrade. Is that true?
Thanks.
Thu, 21/05/2009 - 07:36
#2
0.21 upgrade, other things
Yes, it was an upgrade from 0.19 and it went as hoped, uneventful. There was an error later working on something, but it worked itself out. I find a few other things I had trouble with.
- The sample stories I entered, several of them didn't have enough room for the cutline. Is there a way I can change that?
- On the image gallery, if there is content in the left sidebar block, the images overlap the text?
- How do I get to the blogs and create a menu option to access them?
- When I am selecting a story to put in a custom block, the story list that pops up only has a few of the stories in it. How do I see the other stories other than going back out?
- Also in the custom block, I couldn't get one of the stories (Grad student) to go to the top. I moved it there, but it doesn't display at the top. I made sure to save the individual block and blocks. I couldn't find any options that would prevent it from doing so. Would something category ratings have something to do with that?
I am an intern working on the Patriot Talon website for the University of Texas at Tyler. Their current website is at http://www.patriottalon.com. The Prosepoint site I am working on is at http://www.patriottalon.info. BTW, it looks like it will be a big improvement over the current Wordpress system.
Thanks,
Thu, 21/05/2009 - 10:19
#3
...
Hi,
> The sample stories I entered, several of them didn't have enough room for
> the cutline. Is there a way I can change that?
By 'cutline', I think you mean the teaser (in ProsePoint terminology). Normally, ProsePoint automatically computes the teaser (but you can configure the length at .../admin/content/node-settings -> Length of trimmed posts). However, you can also override this in the editor.
On the visual editor, there is a Teaser Break button next to the Insert Image button. Inserting a teaser break into your story will tell ProsePoint where the teaser should end.
> On the image gallery, if there is content in the left sidebar block, the images overlap the text?
Ah, this would be a bug :) I probably should add some settings to make the image size used by the gallery, and the number of columns in the gallery configurable.
For now, if you don't mind wading in more advanced parts of ProsePoint/Drupal, I can supply some information on how to change this.
> How do I get to the blogs and create a menu option to access them?
By blogs, I presume you mean channels operating in story listing mode. Visit .../admin/content/channels on your site, pick a channel of interest, and click on edit. Under the fieldset Channel settings, there should be a further fieldset which lets you add/edit a menu entry for the channel.
Note the menus are also editable from the page .../admin/build/menu. The previous method was just a shorthand way of editing menus. Doing it from .../admin/build/menu presents the full interface.
> When I am selecting a story to put in a custom block, the story list that
> pops up only has a few of the stories in it. How do I see the other stories other than going back out?
There could be a few things happening here, and I'm not quite sure I understand your question. If you visit the Story Manager at .../admin/content/stories, does that help?
> Also in the custom block, I couldn't get one of the stories (Grad student) to go to the top.
And this is where I'm also a bit confused (probably due to terminology). Are you talking about a channel block as listed in .../admin/build/block? Or a channel sub-block which is turned on when you use editions with composite layout?
Or are you not talking about blocks at all, but actually meaning editions and the ordering of Headlines or Other Stories stories?
Fri, 22/05/2009 - 01:39
#4
cutline or caption too short
I'll respond individually to each point so it will be easier for future readers.
>> The sample stories I entered, several of them didn't have enough room for
>> the cutline. Is there a way I can change that?
>By 'cutline', I think you mean the teaser (in ProsePoint terminology). Normally, ProsePoint automatically computes the teaser (but you can configure the length at .../admin/content/node-settings -> Length of trimmed posts). However, you can also override this in the editor.
>On the visual editor, there is a Teaser Break button next to the Insert Image button. Inserting a teaser break into your story will tell ProsePoint where the teaser should end.
No, not the teaser. Actually, caption is the term used here, the text displayed beneath a picture. Some of the captions have a description and then a long lists of names.
Fri, 22/05/2009 - 01:41
#5
gallery images and text overlap
>> On the image gallery, if there is content in the left sidebar block, the images overlap the text?
>Ah, this would be a bug :) I probably should add some settings to make the image size used by the gallery, and the number of columns in the gallery configurable.
>For now, if you don't mind wading in more advanced parts of ProsePoint/Drupal, I can supply some information on how to change this.
I simply avoided using the left sidebar block on gallery pages. I would be happy to make the changes, and assume you will be making the same changes for future releases. Is that something that can also be modified in my subtheme or something?
Fri, 22/05/2009 - 01:42
#6
linking to the blogs.
>> How do I get to the blogs and create a menu option to access them?
>By blogs, I presume you mean channels operating in story listing mode. Visit .../admin/content/channels on your site, pick a channel of interest, and click on edit. Under the fieldset Channel settings, there should be a further fieldset which lets you add/edit a menu entry for the channel.
>Note the menus are also editable from the page .../admin/build/menu. The previous method was just a shorthand way of editing menus. Doing it from .../admin/build/menu presents the full interface.
That one I figured out. I had added a channel with "Blogs" and tried to add a menu items with that name like I thought I did with the other channels, and it was always blank.
I discovered from the backlink from my blog entry that the internal link for the blogs channel is "blog". Then I manually set up an alias to use in the menus. Works fine for now.
Now I need to do some study to see how to just list the individual blogs and not all of the blog entries...
Fri, 22/05/2009 - 01:50
#7
> Also in the custom block, I
>> Also in the custom block, I couldn't get one of the stories (Grad student) to go to the top.
>And this is where I'm also a bit confused (probably due to terminology). Are you talking about a channel block as listed in .../admin/build/block? Or a channel sub-block which is turned on when you use editions with composite layout?
>Or are you not talking about blocks at all, but actually meaning editions and the ordering of Headlines or Other Stories stories?
No, it's not really an edition, but it does use Headlines and Other Stories. I am using a simulated type of edition by using selected stories in a channel.
I created a channel for "Featured News"
I set the Frontpage to display the channel "Featured News", even though it is empty.
I go to Content Management > Blocks and select the "Featured News" channel for the top content and then "configure" it to use selected headlines and include four stories. I put the fourth story at the top of the list, save and save, but when it is displayed, that story is always at the bottom. I checked and the top story is neither promoted or sticky. I also cleared the cache and refreshed the browser. Even reordered the channels to see if that made a difference.
I managed to move the other three stories around earlier.
Sat, 23/05/2009 - 11:07
#8
Many replies ...
Hi,
Image captions
The caption for images isn't meant to contain anything fancy such as html tags or lists. I think the editor gets confused.
You can certainly try putting in multiple lines and html lists, but don't be surprised if it breaks. If you try this, I'd suggest switching the editor to HTML mode and entering the HTML code by hand inside the <pp_img> tag.
In the short to medium term, I'm not sure what I can do about this. It's not really feasible to handle any arbitrary content in the image captions.
Image gallery
The gallery is defined by the View images_list -> Gallery viewer display. If you enable the module Views UI, you can edit this and play around with it yourself. Any changes you make merely override the default view definition, so you can always revert by deleting the view.
If user-friendly gallery configuration settings were to be added in future ProsePoint releases (and I have noted it as a feature request), I'd probably have to change the view, in which case you'd have to revert your view to pick up the changes.
You can't easily change the content of the gallery from a theme. ProsePoint/Drupal has strong separation between content and presentation, and things like 'number of columns in a table' need to be changed at the content level, not the presentation level.
(As an aside, if you want to add this feature yourself, please let me know and I'll help you develop a patch)
Blogs
I think there might be some possibility for confusion here. ProsePoint has channels which, when operating in story listing mode, look like blogs and can be used as such.
There is also a core module Blog which enable's Drupal's version of blogs. Just be aware of this. There are subtle differences between the two, but as long as you know which one you're using, go ahead and use whichever you like.
Channel block
Hmmm... You might be right. There may be a bug with respecting the ordering of the Headlines field for Channel blocks and Channel sub-blocks. Let me investigate this and get back to you.
Hi,
Would that be upgrading to ProsePoint 0.21? It'd be good to know if things are going okay out in the wild.
> I was wondering, however, about the difference in procedures.
It's just a case of keeping things under control and trying to reduce the chances of problems occurring. Since there are so many Drupal modules around, and an infinite number of permutations, trying to support upgrades for any combination of modules probably requires too much effort. If Drupal was always upgraded with contributed modules disabled, then the core developers have some hope of reproducing and hence, debugging issues.
ProsePoint is under similar constraints, but to a different degree. We don't support modules other than the ones included in the standard package, but we can't (and won't) stop people adding Drupal modules to their sites themselves either. However, if they do that, any problems are their issue.
However, we do support upgrading ProsePoint as a whole because we test the combination of modules (and other stuff) that is ProsePoint, so we're much more comfortable with it. In fact, a ProsePoint upgrade actually relies on the ProsePoint standard modules being available, otherwise things will break.
So, please don't disable ProsePoint modules when upgrading (but you can disable any extra Drupal modules you add yourself).