1
greyhair
Re: gallery 2 was Upgrade Smarty?
  • 2005/10/16 21:44

  • greyhair

  • Just popping in

  • Posts: 12

  • Since: 2004/4/7 1


see this post at xoopsgallery.org



2
greyhair
Re: gallery 2 was Upgrade Smarty?
  • 2005/10/16 21:42

  • greyhair

  • Just popping in

  • Posts: 12

  • Since: 2004/4/7 1


So far install process goes something like this (outline):
1. update smarty <-- d/l from smarty.php.net and copy the contents lib folder to xoopsrootfolder/class/smarty (very breif discription)
2. upload xoopsgallery2 module files <-- I'm going to encorporate the gallery2 files in with my module files for ease
3. follow install process for gallery2 <-- the G2 program is still a stand alone program (makes upgrading gallery2 a snap, I hope).
4. initialize xoopsgallery2 module <-- just like any XOOPS module
5. fill in appropriate info in xoopsgallery2 admin section <-- again, just like any XOOPS module
6. done? <-- this is a very breif outline there may be a bit more to it!!



3
greyhair
Re: Upgrade Smarty?
  • 2005/10/16 5:33

  • greyhair

  • Just popping in

  • Posts: 12

  • Since: 2004/4/7 1


To whom can I send this request? I would like XOOPS to upgrade their smarty engine to 2.6.10.

Please!



4
greyhair
Upgrade Smarty?
  • 2005/10/3 4:07

  • greyhair

  • Just popping in

  • Posts: 12

  • Since: 2004/4/7 1


Hi all. My feature request is to have the XOOPS smarty template engine upgraded (updataed) to 2.6.10.

I'm trying to get Gallery 2 (http://gallery.sf.net) up and running as a XOOPS module for http://xoopsgallery.org.

Everything works well if I upgrade the smarty engine used by XOOPS to 2.6.10. Currently the XOOPS smarty engine is 2.6.5-dev.

I replaced the old smarty engine with the new and have no issues, yet. Of course, I’m focusing on the gallery2 module development and haven't looked at other modules that could be affected.

Some advice in this matter would be appreciated.



5
greyhair
pass headlines rss thru textsanitizer, Possible?
  • 2005/2/4 7:28

  • greyhair

  • Just popping in

  • Posts: 12

  • Since: 2004/4/7 1


Is it possible to pass the headline data through the textsanitiser to convert the non xhtml compliant parts like the "&" and others?

Could you post how, what and where, Please.

Thanks



6
greyhair
Re:Help on modifing the register page
  • 2004/10/26 3:59

  • greyhair

  • Just popping in

  • Posts: 12

  • Since: 2004/4/7 1


oops:

From Mithrandir in a earlier post


Quote:
... You give 6 parameters to a constructor taking 5.

$formmpegid = new XoopsFormText(_AM_DEBASER_ID'mpegid'44$xfid);
$formmpegid->setExtra('extra code goes here');


would be the way to set the _extra property.



7
greyhair
Re:Help on modifing the register page
  • 2004/10/26 3:46

  • greyhair

  • Just popping in

  • Posts: 12

  • Since: 2004/4/7 1


looks like getExtra is not defined in formtext.php (i have v 1.7) once i did that it worked. Thanks.



8
greyhair
Help on modifing the register page
  • 2004/10/25 21:12

  • greyhair

  • Just popping in

  • Posts: 12

  • Since: 2004/4/7 1


Hi. I haven't search long (as i'm at work...) and would like some direction on how to modify the register page.

I would like to try to improve what information is required in which fields like this for a text field: (email address field for this example)

value="Enter Email Address" ONFOCUS="if(this.value=='Enter Email Address')this.value='';" ONBLUR="if(this.value=='')this.value='Enter Email Address';">

Is there a XOOPS way to input this extra stuff? MOre over, how could i send this type of information to "$this->getExtra()" in formtext.php?

I dont see a register template.

Thanks in advance for any help!



9
greyhair
Error in comment_form.php line 110
  • 2004/10/7 4:26

  • greyhair

  • Just popping in

  • Posts: 12

  • Since: 2004/4/7 1


hi.

Should this be fixed in include/comment_form.php to say $_POST instead?

line 110:

if (isset($_POSTS[$extra_param])) {



10
greyhair
Request: encode urls in xoopsheadline module
  • 2004/7/12 13:02

  • greyhair

  • Just popping in

  • Posts: 12

  • Since: 2004/4/7 1


This is very picky but, special html characters are not supposed to be in an url. Can someone show me how to use htmlspecialchars() to encode xoopsheadline urls? At least i think htmlspecialchars() is the proper php function to use...

I would like to pass http://validator.w3.org with the xoopsheadline page.

The feature request: the ability to turn this feature on and off in the admin area (once the encoding method is proven)!!

Thanks.

This is also posted here (by n00b accident).




TopTop
(1) 2 »



Login

Who's Online

48 user(s) are online (28 user(s) are browsing Support Forums)


Members: 0


Guests: 48


more...

Donat-O-Meter

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

Latest GitHub Commits