292062
One feature that would make it better would be to have the ability to search via letter e.g. clicking on R would bring up all the listings in that category that start with an R.
It would make finding a particular business easier.
Also searching by Town/City would be nice.
It would make finding a particular business easier.
Also searching by Town/City would be nice.
292063
is the module available for download?
or for testing purposes?
Thanks
Its a great superb module~~
or for testing purposes?
Thanks
Its a great superb module~~
292064
Hi there,
Thanks for that. I went through with Dreamweaver and hunted down each instance and replaced what was needed. It looks close, but still some bugs.
FYI...my module is to be called "sportsdraw"
1, 2, 3, 4....done
Quote:
Not sure what you mean here?
Quote:
I could only find those two instances...no others. Point 7, of course I'll leave in the credits!
OK...back to point 6...I'm not sure if this is the right thing to do? When starting up Xoops, the first thing I notice is that the image/icon for this module isn't showing. Looking at the source code, I see the url listed as....
http://127.0.0.1/xoops/modules/_MI_SPORTSDRAW_DIR_NAME/images/logo.png
So maybe I misinterpretted what you meant in point 6?
Installing the module appears to work, but then you get it listed as "Module File for Not Found!", with a broken image and a version setting of '0'.....so I don't think it has worked.
I'm also not sure if the sql functions were actually carried out and if I was meant to update any sql?
Cheers,
Phil
Thanks for that. I went through with Dreamweaver and hunted down each instance and replaced what was needed. It looks close, but still some bugs.
FYI...my module is to be called "sportsdraw"
1, 2, 3, 4....done
Quote:
5) Replace the necessary language constants in the language files
Not sure what you mean here?
Quote:
6) And most important, open xoops_version.php and replace the two instances of "_MI_DIR_NAME" for "_MI_MODULENAME_DIR_NAME". In fact, also make this replacement directory wide.
I could only find those two instances...no others. Point 7, of course I'll leave in the credits!
OK...back to point 6...I'm not sure if this is the right thing to do? When starting up Xoops, the first thing I notice is that the image/icon for this module isn't showing. Looking at the source code, I see the url listed as....
http://127.0.0.1/xoops/modules/_MI_SPORTSDRAW_DIR_NAME/images/logo.png
So maybe I misinterpretted what you meant in point 6?
Installing the module appears to work, but then you get it listed as "Module File for Not Found!", with a broken image and a version setting of '0'.....so I don't think it has worked.
I'm also not sure if the sql functions were actually carried out and if I was meant to update any sql?
Cheers,
Phil
292065
@ Philroy:
Cloning Tiny Content it's not hard at all. What you have to do is a lot of replacements:
1) Replace every instance of "_TINYCONTENT_" with "_YOURMODULENAME_".
2) Replace every instance of "tinycontent" with "yourmodulename".
3) Replave every instance of "_TC_" with "_YOURMODULENAME_".
4) Change the names of three files:
-- blocks/tc_navigation.php
-- templates/tinycontent_index.html
-- templates/blocks/tinycontent_navigation_block.html
to
-- blocks/yourmodulename_navigation.php
-- templates/yourmodulename_index.html
-- templates/blocks/yourmodulename_navigation_block.html
5) Replace the necessary language constants in the language files
6) And most important, open xoops_version.php and replace the two instances of "_MI_DIR_NAME" for "_MI_MODULENAME_DIR_NAME". In fact, also make this replacement directory wide.
7) Also very important: do whatever changes you need, but please leave Chapi's credits in their place. It's his work and won't cost you anything to have this credits there.
I think that's all. If you have any problems, please post them here to make the necessary corrections.
Cheers.
Cloning Tiny Content it's not hard at all. What you have to do is a lot of replacements:
1) Replace every instance of "_TINYCONTENT_" with "_YOURMODULENAME_".
2) Replace every instance of "tinycontent" with "yourmodulename".
3) Replave every instance of "_TC_" with "_YOURMODULENAME_".
4) Change the names of three files:
-- blocks/tc_navigation.php
-- templates/tinycontent_index.html
-- templates/blocks/tinycontent_navigation_block.html
to
-- blocks/yourmodulename_navigation.php
-- templates/yourmodulename_index.html
-- templates/blocks/yourmodulename_navigation_block.html
5) Replace the necessary language constants in the language files
6) And most important, open xoops_version.php and replace the two instances of "_MI_DIR_NAME" for "_MI_MODULENAME_DIR_NAME". In fact, also make this replacement directory wide.
7) Also very important: do whatever changes you need, but please leave Chapi's credits in their place. It's his work and won't cost you anything to have this credits there.
I think that's all. If you have any problems, please post them here to make the necessary corrections.
Cheers.
292066
@ Philroy:
Cloning Tiny Content it's not hard at all. What you have to do is a lot of replacements:
1) Replace every instance of "_TINYCONTENT_" with "_YOURMODULENAME_".
2) Replace every instance of "tinycontent" with "yourmodulename".
3) Replave every instance of "_TC_" with "_YOURMODULENAME_".
4) Change the names of three files:
-- blocks/tc_navigation.php
-- templates/tinycontent_index.html
-- templates/blocks/tinycontent_navigation_block.html
to
-- blocks/yourmodulename_navigation.php
-- templates/yourmodulename_index.html
-- templates/blocks/yourmodulename_navigation_block.html
5) Replace the necessary language constants in the language files
6) And most important, open xoops_version.php and replace the two instances of "_MI_DIR_NAME" for "_MI_MODULENAME_DIR_NAME".
7) Also very important: do whatever changes you need, but please leave Chapi's credits in their place. It's his work and won't cost you anything to have this credits there.
I think that's all. If you have any problems, please post them here to make the necessary corrections.
Cheers.
Cloning Tiny Content it's not hard at all. What you have to do is a lot of replacements:
1) Replace every instance of "_TINYCONTENT_" with "_YOURMODULENAME_".
2) Replace every instance of "tinycontent" with "yourmodulename".
3) Replave every instance of "_TC_" with "_YOURMODULENAME_".
4) Change the names of three files:
-- blocks/tc_navigation.php
-- templates/tinycontent_index.html
-- templates/blocks/tinycontent_navigation_block.html
to
-- blocks/yourmodulename_navigation.php
-- templates/yourmodulename_index.html
-- templates/blocks/yourmodulename_navigation_block.html
5) Replace the necessary language constants in the language files
6) And most important, open xoops_version.php and replace the two instances of "_MI_DIR_NAME" for "_MI_MODULENAME_DIR_NAME".
7) Also very important: do whatever changes you need, but please leave Chapi's credits in their place. It's his work and won't cost you anything to have this credits there.
I think that's all. If you have any problems, please post them here to make the necessary corrections.
Cheers.
292067
Hi,
I started out with a copy of the default theme and then modified the main theme html file. This file arranges the main layout of the website. All the mouseover action is done in css in the same theme directory.
What is also usefull is the possibility to change template files using the administration menu. However, to do so you should clone the default template set (see templates menu) and edit the custom template set.
I hope this helps you a little. If you need any specific information please let me know.
Martijn
Quote:
I started out with a copy of the default theme and then modified the main theme html file. This file arranges the main layout of the website. All the mouseover action is done in css in the same theme directory.
What is also usefull is the possibility to change template files using the administration menu. However, to do so you should clone the default template set (see templates menu) and edit the custom template set.
I hope this helps you a little. If you need any specific information please let me know.
Martijn
Quote:
First, did you begin with a fresh template theme? Or did you modify the default?
...
But mainly, the link action in the main menu, is that part of the CCS?
292068
What XOOPS needs (and probably a lot of other CMS) is a kind of frames module, that allows XOOPS to wrap around existing web pages. I'm also working on a school website, and I'm thinking of just creating a new template for all my pages that looks like the one I'm using with Xoops. Then I'll probably use iMenu for the links.
imenue
The user won't know the difference.
You can also create your own mod see here. You may have to register to see this link.
I made a very simple "mod". Simply a folder with index.php and xoops_version.php. The index.php file contained a few links, nothing more. What would be nice is if upon pressing a link, the content stayed inside xoops. Anyone?
Which brings me to a general question. XOOPS is great as it links together some important things: forum, calendar (like Agenda-x), faq, etc., which are all searchable as they are part of the same system. However, most of the CMS that I've looked at don't account for site with lots of pages. For example: On a school site we might want to have pages for every class, club and program. What's the best way to get these pages up?
Sections is content, but mostly text.
Freecontent, etc., seems like a good alternative, but what if my content has child pages? Do those stay in the XOOPS wrap?
imenue
The user won't know the difference.
You can also create your own mod see here. You may have to register to see this link.
I made a very simple "mod". Simply a folder with index.php and xoops_version.php. The index.php file contained a few links, nothing more. What would be nice is if upon pressing a link, the content stayed inside xoops. Anyone?
Which brings me to a general question. XOOPS is great as it links together some important things: forum, calendar (like Agenda-x), faq, etc., which are all searchable as they are part of the same system. However, most of the CMS that I've looked at don't account for site with lots of pages. For example: On a school site we might want to have pages for every class, club and program. What's the best way to get these pages up?
Sections is content, but mostly text.
Freecontent, etc., seems like a good alternative, but what if my content has child pages? Do those stay in the XOOPS wrap?
292069
Quote:
Hmm...any advice anyone on how to clone Tiny Content? It's not as easy as duplicating the folder as there are database conflicts, so I think I need to update HTML pages and MySQL in the module.
I posted on the site that Tiny Content comes from, but am yet to get a reply.
Phil
1) You seem to have three content sections, each with several pages. I'd make three clones of Tiny Content and name them "About PNINS", "Events" and "Teams". Then I'd feed the content using Tiny Content's editor, in order to build the navigation block. An at the end, I'd put the three navigation blocks together to form the complete left menu. This way, you'll be able to edit every page using Tiny Content's built-in editor.
Hmm...any advice anyone on how to clone Tiny Content? It's not as easy as duplicating the folder as there are database conflicts, so I think I need to update HTML pages and MySQL in the module.
I posted on the site that Tiny Content comes from, but am yet to get a reply.
Phil
292070
Quote:
First, did you begin with a fresh template theme? Or did you modify the default?
Second, shop question already answered.
But mainly, the link action in the main menu, is that part of the CCS?
That would be a lot of pointers . What would you like to know?
First, did you begin with a fresh template theme? Or did you modify the default?
Second, shop question already answered.
But mainly, the link action in the main menu, is that part of the CCS?
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|