21
ibzan
xp-weather 1.4
  • 2003/11/7 11:15

  • ibzan

  • Just popping in

  • Posts: 48

  • Since: 2003/8/31


Has anybody figured out a way to get xp-weather to work with a XOOPS version later than 2.0.2?
Great little module, would be nice to see it keep up with the more current versions of Xoops.

Chris



22
ibzan
Re: XOOPS 2.1 Core development Roadmap
  • 2003/11/7 8:37

  • ibzan

  • Just popping in

  • Posts: 48

  • Since: 2003/8/31


1) Multi-lingual friendly (or friendlier if you want) keeping in mind not only admin / programmer types but also average users who add content.
I did like what I had read over at Xaraya's site about the ability to turn off this feature to enhance performance in need be. But if the feature is needed, allow it at the cost of a bit of performance.
This should be something handled at the back-end exclusively. There is too much to get wrong by hacking the core for inexperienced people.
I think out of the box XOOPS should be multi-lingual because this will also force module development with this in mind.

2) Better detailed documentation.

3) I totally agree with sunsnapper's though concerning the theme management by better utalizing DIVs via CSS, etc. Seemingly a bit complex to start with, however EXTREMELY powerful. This really brings the page out of the box and gives much more freedom to designers.


4) both the ability to control access via groups but allow also for individual access (may actually be redundant or too slow?) I am open to be wrong :)

blessings,

Chris



23
ibzan
Re: LEECH ANY THEME EASILY ;-) FROM XOOPS2
  • 2003/11/7 8:25

  • ibzan

  • Just popping in

  • Posts: 48

  • Since: 2003/8/31


I was under the impression that servers could (if not should) be set up to disallow direct access to these types of directories - i.e. an unidentified user does not have full access, but the system does and when the system calls for a file it has access, however if a user simply types a URL directly to, say the css file, it will be denied.

Leeching is pretty lame, and in my estimation show a lack of creativity and effort to make something unique. Some stuff is great to learn from, but you'll never learn from simply copying. If you want to learn css, there are some GREAT sites that have both overall as well as step by steb guides for all levels of understanding.

Well that was my two cents worth



24
ibzan
Re: SOLVED - Making Xoops CONTENT Multilingual *Fixed Code Quote problem*
  • 2003/11/7 8:17

  • ibzan

  • Just popping in

  • Posts: 48

  • Since: 2003/8/31


I haven't see this question asked at all and was wondering if I was the only one who was thinking about this.

Switching languages seems to have been worked out for the time being, but I have noticed that the date function is still returning English names for the months and days.

Is this:

a) a server issue? I mean that what ever local is set on the server is what the date function will will return.

b) a local computer issue? what ever local on the users computer is what the date function looks at to return

c) something alltogether different?

In the global.php file the only settings for how date and time are displayed are the relivent PHP variables for the date function. So.... how can I (or anybody else) get it to also switch the names for the days and months.

Any ideas?

blessings,

Chris



25
ibzan
Re: SOLVED - Making Xoops CONTENT Multilingual *Fixed Code Quote problem*
  • 2003/11/7 8:11

  • ibzan

  • Just popping in

  • Posts: 48

  • Since: 2003/8/31


Hmm, I figured it out - what was not mentioned was that the

Quote:
$myts =& MyTextSanitizer::getInstance();


also needs to be entered. No big deal, though maybe somebody else also had this problem.

Chris



26
ibzan
Re: SOLVED - Making Xoops CONTENT Multilingual *Fixed Code Quote problem*
  • 2003/11/7 7:49

  • ibzan

  • Just popping in

  • Posts: 48

  • Since: 2003/8/31


Quote:
Where it says
[quote]$modules[$i]->getVar('name')


I put
Quote:
$myts->makeTboxData4Show($modules[$i]->getVar('name'))


I come up with a blank page with this hack. Don't know why?!? The one for the sublinks works great. Is this because the header.php needs to be updated too? I didn't understand that be the case though.

Chris



27
ibzan
Re: wfsections WYSIWYG editor bug?
  • 2003/11/7 7:40

  • ibzan

  • Just popping in

  • Posts: 48

  • Since: 2003/8/31


Quote:
Yes I agree that this would be helpfull to everyone out there.
you just put another few days on the release LOL


Shame on me



28
ibzan
Re: wfsections WYSIWYG editor bug?
  • 2003/11/7 7:33

  • ibzan

  • Just popping in

  • Posts: 48

  • Since: 2003/8/31


Quote:
Instead, WF will use a very heavily modified SPAW WYSIWYG editor and I hopefully have fixed many of the problems related with the previous versions in this area.


Great to hear! One thought may be of some use... (yep more free advice )

Instead of having to switch from the WSYIWYG editor to the XOOPS editor from within the preferances, might it be helpful to allow the switch the same way we now currently switch from teh WSYIWYG editor to the HTML? Kind of like either a button the cycles between all three, or a seperate link opposite the WSYIWYG / HTML editor to switch between XOOPS and WSYIWYG.

blessings,

Chris



29
ibzan
Re: Great Calendar Module!
  • 2003/11/7 7:26

  • ibzan

  • Just popping in

  • Posts: 48

  • Since: 2003/8/31


Though my wish list has always included a port of PostCalendar, PiCal is by far the best I have yet seen for Xoops; even includes a couple of features which PostCalendar doesn't.
Very Impressed. I will be following this calendar. I would like to see a little more attention on the look of the calendar. The back-end has obviously had some serious attention, but the front-end looks like it needs a bit of a make over

Chris



30
ibzan
wfsections WYSIWYG editor bug?
  • 2003/11/6 18:51

  • ibzan

  • Just popping in

  • Posts: 48

  • Since: 2003/8/31


I had been using the WYSIWYG editor (mostly in the view HTML mode) within the wfsection module for a while with no problems. Then while updating an article when it posted the HTML code I had entered came right along into the file, ie. not recognized as HTML and the whole article was screwed up.
The only way I got around this was to turn it off and only use the XOOPS editor.
Has anybody else ran into this?

Chris




TopTop
« 1 2 (3) 4 5 »



Login

Who's Online

203 user(s) are online (145 user(s) are browsing Support Forums)


Members: 0


Guests: 203


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits