102
@ Knuxchan
I needed it then not for "breaking the loop" but for dividing it into 2 colums
I needed to divide string of 10 results into 2 colums of 5 results .... so my solution was good for my needs - not for yours
That one .... was long ago ... 2 years ... when the world was young
I needed it then not for "breaking the loop" but for dividing it into 2 colums
I needed to divide string of 10 results into 2 colums of 5 results .... so my solution was good for my needs - not for yours
That one .... was long ago ... 2 years ... when the world was young
103
@ all
I'm using article version 1 since it came out.
It's potential is high, highly configurable especially for XOOPS pro's ..... friendly url's .... each category can look and act completely different , and so on ....
It was always my selection when using an article module. . . . . BUT !!!!!!!!!!!!!!!!!!!
It's a bit confusing to my editors (I too wonder what is the difference between SUBMITTED , PUBLISHED , CREATED , REGISTERED , REGULAR ... )
It's spotlight is too simple (must have more options and multi-articles ability)
It has to have some gadgets for embedding in articles ( info balloons as was introduced in the "long-forgotten" magazine module)
I can count a lot more, but it'll be useless !!!
I'm just saying that for a long time I wonder "why do this powerful module deserve this treatment ?" - it deserves to be one of the most "spoiled" modules since it's so versatile and since XOOPS is a "FRAMEWORKS" and the module supposed to be the CMS running on it.
as if no-one really wants to be the "loving father" of this nice child.
I'm using article version 1 since it came out.
It's potential is high, highly configurable especially for XOOPS pro's ..... friendly url's .... each category can look and act completely different , and so on ....
It was always my selection when using an article module. . . . . BUT !!!!!!!!!!!!!!!!!!!
It's a bit confusing to my editors (I too wonder what is the difference between SUBMITTED , PUBLISHED , CREATED , REGISTERED , REGULAR ... )
It's spotlight is too simple (must have more options and multi-articles ability)
It has to have some gadgets for embedding in articles ( info balloons as was introduced in the "long-forgotten" magazine module)
I can count a lot more, but it'll be useless !!!
I'm just saying that for a long time I wonder "why do this powerful module deserve this treatment ?"
- it deserves to be one of the most "spoiled" modules since it's so versatile and since XOOPS is a "FRAMEWORKS" and the module supposed to be the CMS running on it.as if no-one really wants to be the "loving father" of this nice child.
105
Quote:
Were here for a long time .... most xoopers do ....
redheadedrod wrote:
If you are waiting for me to get it done though it may take a little while.. Going to write a couple modules from scratch and tweak with what is here already.. See where that gets me...
Were here for a long time .... most xoopers do ....
106
Quote:
That would be very interesting !!!
redheadedrod wrote:
I was considering a total rewrite of the module to incorporate some serious community site support.
That would be very interesting !!!
107
Hi T
Now Jobs module gives white Screen with
still no-go with the meta-data
tested with xigg & Video-tube ...
Now Jobs module gives white Screen with
Fatal error: Call to a member function on a non-object in /usr/..../..../htdocs/modules/defacer/include/beforeheader.php on line 12
still no-go with the meta-data
tested with xigg & Video-tube ...
109
Hi trabis
I has the same issue too - simply no effect on page title/meta
All green and no debug errors
xoops 2.3.2 , php 4.4
Side effect of the line in header.php - the "jobs" module gives white screen with no errors in debug mode.
I also tryed it with the "planet" , "article" and with "xigg" which has build-in rewrite url in it as default - and wondered which url should be the right one ...
One more thing - is there any point of testing it under 2.2.x branch ?
I has the same issue too - simply no effect on page title/meta
All green and no debug errors
xoops 2.3.2 , php 4.4
Side effect of the line in header.php - the "jobs" module gives white screen with no errors in debug mode.
I also tryed it with the "planet" , "article" and with "xigg" which has build-in rewrite url in it as default - and wondered which url should be the right one ...
One more thing - is there any point of testing it under 2.2.x branch ?
110
10x sarahmx
Quote:
Yes, but again - I think the "profile" module is the most important module in the system, and should include powerful features like import/export users , mass-actions on selected users , ability to control not just the registrations field - but also the registration mail - what will be sent to the admins and what to the users (fields, custom massages and so ...
A big part of a XOOPS site is it's users and the system as is is not giving a decent solution for it !!!
we're all here to contribute and each has his point-of-view on the system (what's good and what's bad) and this is my point of view - I always try not to look from the developer or the admin perspective - but to look from the site-admin or the user perspective ...
I'm not looking for a tmp solution for my current needs , but for improved ability for Xoops.
phpMyAdmin is the solution for me right now, but whenever I use it - I think - "gosh - this things should be part of the system"
Quote:
ghia wrote:
Did you check out this hack from XOOPS China?
Maybe for export it could be added to the user profile search by adding a button that provides the export of all the data for the selected users?
Yes, but again - I think the "profile" module is the most important module in the system, and should include powerful features like import/export users , mass-actions on selected users , ability to control not just the registrations field - but also the registration mail - what will be sent to the admins and what to the users (fields, custom massages and so ...
A big part of a XOOPS site is it's users and the system as is is not giving a decent solution for it !!!
we're all here to contribute and each has his point-of-view on the system (what's good and what's bad) and this is my point of view - I always try not to look from the developer or the admin perspective - but to look from the site-admin or the user perspective ...
I'm not looking for a tmp solution for my current needs , but for improved ability for Xoops.
phpMyAdmin is the solution for me right now, but whenever I use it - I think - "gosh - this things should be part of the system"
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 |
 |
|