22
This is an old thread but I ran across it looking for something else. XoopsGallery 1.3.3.3 is now compatible with Gallery Remote (see the README for instructions).
Also, there is a script available to help migrate a database to XoopsGallery from Gallery.
http://www.sciox.org/xoops/modules/newbb/viewtopic.php?topic_id=42&forum=1&post_id=183#forumpost183
Also, there is a script available to help migrate a database to XoopsGallery from Gallery.
http://www.sciox.org/xoops/modules/newbb/viewtopic.php?topic_id=42&forum=1&post_id=183#forumpost183
23
I just finished up responding to a thread similar to this one on the XoopsGallery site. Suffice to say I've posted a script that I got ahold of awhile ago (although I can't recall where or when) that can help with the migration.
http://www.sciox.org/xoops/modules/newbb/viewtopic.php?topic_id=42&forum=1&post_id=183#forumpost183
http://www.sciox.org/xoops/modules/newbb/viewtopic.php?topic_id=42&forum=1&post_id=183#forumpost183
24
Quote:
I absolutely agree with the granularity issues... and that provides a much more reasonable example for my previous thought (of having what variables are available and their meaning): Backward compatability. I *just* went through this with XoopsGallery. I made a big mistake by not leaving in the old smarty variables when I made the templates more granular. XG used to render half the page with one smarty variable, but now I have that broken out quite a bit to allow the designer more control.
In this particular case, I can see <{$story.morelink}> being seperated into (this is off the top of my head):
That is a LOT of variables for one small section of the block, but it gives total freedom to the designer to implement as they see fit. Some of these (the "text" ones) are likely repetitive to other smarty variables that might already be available.
Now, to the point here: If someone was to patch the News module to do this, what happens to the templates with the old <{$story.morelink}>? How does a template designer know that the old morelink is depricated and the 6 others take it's place other than by comparing versions of templates?
Thanks Draven for already looking at adding this!
Per4orm wrote:
For example, the reason that "Comments?" still appears in articles when comments are disabled, is because the phrase is a composite component of <{$story.morelink}>, which means it cannot simply be removed by editing the template.
...
I absolutely agree with the granularity issues... and that provides a much more reasonable example for my previous thought (of having what variables are available and their meaning): Backward compatability. I *just* went through this with XoopsGallery. I made a big mistake by not leaving in the old smarty variables when I made the templates more granular. XG used to render half the page with one smarty variable, but now I have that broken out quite a bit to allow the designer more control.
In this particular case, I can see <{$story.morelink}> being seperated into (this is off the top of my head):
<{$story.morehref}> URL to full story
<{$story.morehreftext}> Text "Read More..." in selected language
<{$story.morebytes}> # bytes remaining
<{$story.morebytestext}> Text "bytes more" in selected language
<{$story.comhref}> Comments form URL
<{$story.comhreftext}> Text "Comments?" in selected language
That is a LOT of variables for one small section of the block, but it gives total freedom to the designer to implement as they see fit. Some of these (the "text" ones) are likely repetitive to other smarty variables that might already be available.
Now, to the point here: If someone was to patch the News module to do this, what happens to the templates with the old <{$story.morelink}>? How does a template designer know that the old morelink is depricated and the 6 others take it's place other than by comparing versions of templates?
Thanks Draven for already looking at adding this!
25
Quote:
Yes, it certainly would. Thanks!
Draven wrote:
Gstarrett, I'll tell you what, would it help if I made a header comment outlining all the variables and their use for each template? It wouldn't take too much effort to add this when I'm making the default templates. Perhaps this would act as a mini guide for each template and all the available variables and their uses. Just a thought.
Yes, it certainly would. Thanks!
26
If you add that to the bugtracker on the XoopsGallery support site, I'll look into fixing it.
(I'll try to look into it either way, but it won't be forgotten if you post the report to the bug tracker).
(I'll try to look into it either way, but it won't be forgotten if you post the report to the bug tracker).
27
I've used PHP in my template successfully, but I used it to calculate and assign the result to smarty variables. I had also tried to go the include route, but it wasn't practical AFAICT. See the thread for more information:
https://xoops.org/modules/newbb/viewtopic.php?topic_id=10817&forum=5#forumpost43374
https://xoops.org/modules/newbb/viewtopic.php?topic_id=10817&forum=5#forumpost43374
28
Quote:
Yes! Some sort of standard way of describing the smarty variables exposed per module and their definitions. I haven't looked into many templates {whisks off to spot check a few standard templates....} but as it is the web designer would have to basially reverse-engineer the variables from the existing layout. Not hard, but something every designer will have to do with every module they want to create a template for.
Some sort of xoops_version entry or text file or even standard comment block would go a long way to making it easier to find the name and meaning of smarty variables output by modules / block functions.
This is even more important if the module designer includes some "extra" variables that aren't in the default template set and wants them to be discoverable by a web designer. For example, a news item doesn't contain a smarty variable for number of posts by the author, but what if the module designer added it only to the module "in case" someone wanted it? Granted, this might not be the best example but I hope you can see where I'm going with it.
hsalazar wrote:
4) Having said all this, I wouldn't really want to start a discussion about this matter, so I rest my case just saying I'd like the definition of variables to be in the hands of the site manager and the definition of the presentation layer in the hands of the site designer.
Yes! Some sort of standard way of describing the smarty variables exposed per module and their definitions. I haven't looked into many templates {whisks off to spot check a few standard templates....} but as it is the web designer would have to basially reverse-engineer the variables from the existing layout. Not hard, but something every designer will have to do with every module they want to create a template for.
Some sort of xoops_version entry or text file or even standard comment block would go a long way to making it easier to find the name and meaning of smarty variables output by modules / block functions.
This is even more important if the module designer includes some "extra" variables that aren't in the default template set and wants them to be discoverable by a web designer. For example, a news item doesn't contain a smarty variable for number of posts by the author, but what if the module designer added it only to the module "in case" someone wanted it? Granted, this might not be the best example but I hope you can see where I'm going with it.
29
Quote:
It sounds like instead of "updating" the module (as the readme instructs you to) you did a full reinstall. That will cause an update too, but it deletes all your photos in the process.
The show date option is just part of the XOOPS block options, stored in the database like other block options. I'm not sure why you would be having trouble with that, it works fine here. What version of XOOPS are you running?
As for file permissions, yes there are some requirements outlined in the readme file (called "README_XOOPS.txt" in the xoopsgallery directory).
nuker wrote:
aha, that fixed the problem, but...
now the random picture block doens't randomly display the photos, and whenever i try to disable the date display in the block it doesn't save the setting...
update i uninstalled and reinstalled the module. good thing i only had a few pics! the random block is fine now, but for somereason, the show date always remains checked off.
is there a file permission i should be checking?
It sounds like instead of "updating" the module (as the readme instructs you to) you did a full reinstall. That will cause an update too, but it deletes all your photos in the process.
The show date option is just part of the XOOPS block options, stored in the database like other block options. I'm not sure why you would be having trouble with that, it works fine here. What version of XOOPS are you running?
As for file permissions, yes there are some requirements outlined in the readme file (called "README_XOOPS.txt" in the xoopsgallery directory).
30
I agree! It seems there are some bugs (e.g. comments? on news item with comments disables, same with smileys), and just a couple of template granularity issues. Nothing show-stopping by any means.
It also seems there is a bit of variety in the desired strip-down levels. I'd suggest everyone post their ideas on what they think a "professional" template for news, etc. would contain or not contain. We shouldn't worry about agreement, but rather to make sure that there are a template edits or option to disable functions to cover the majority of the diverse needs.
That's my 0.02
It also seems there is a bit of variety in the desired strip-down levels. I'd suggest everyone post their ideas on what they think a "professional" template for news, etc. would contain or not contain. We shouldn't worry about agreement, but rather to make sure that there are a template edits or option to disable functions to cover the majority of the diverse needs.
That's my 0.02
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | May 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|