Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - bigwave

Pages: 1 2 [3]
Discussion & Troubleshooting / Re: <br /> added in description with html
« on: September 03, 2006, 08:23:23 AM »
That was It!  Got what I wanted.  Thanks again Mr. V@no!


Discussion & Troubleshooting / Re: <br /> added in description with html
« on: September 03, 2006, 04:30:04 AM »
Thanks for the advice--I'm not hitting enter keys--I'm doing development in a html editor and cutting and pasting the resulting tables into the image description box--some mechanism then puts <br /> after each html element (if it’s on its own line) which screws up the alignment--now I can (will have to for now) find replace all the newlines with a space so there is one big line but that is hard to edit later.  I was thinking that there was some programming mechanism which is inserting the <br />s which might be able to be turned off so I could keep a lucid html structure for me and others to edit later?

Thanks again,


Discussion & Troubleshooting / <br /> added in description with html
« on: September 02, 2006, 03:42:14 AM »

When I add html to the description box of an image each new line gets replaced by a <br /> such as:  <table><br /> <tr><br /><td> </td><br />.  The fix is to get rid of all the new lines before entering the code in the box but I was wondering if there is a way to switch this off  so there are no <br /> unless I put them in the code.




Mods & Plugins (Releases & Support) / Re: [MOD] Multi-Lightboxes v1.03.1
« on: August 07, 2006, 01:57:40 AM »
Hello Mr.V@ao,

Yes sir, that was it!

Back in business--thank you very much!



Mods & Plugins (Releases & Support) / Re: [MOD] Multi-Lightboxes v1.03.1
« on: August 06, 2006, 11:51:49 PM »
Sorry I forgot to include this in the previous post

This is line 185 that the error in my lightbox.php  refers to:
$msg = (empty($msg)) ? "" : get_msg($msg);

Thanks again!


Mods & Plugins (Releases & Support) / Re: [MOD] Multi-Lightboxes v1.03.1
« on: August 06, 2006, 11:44:14 PM »

Hit a little error here when I try to add or delete lightboxs from the lightbox manage page:
Fatal error: Call to undefined function: get_msg() in /home/iplaceg1/public_html/maui-tropica/maui-tropica-gallery/lightbox.php on line 185



Discussion & Troubleshooting / Re: invalid xml error
« on: August 03, 2006, 05:46:22 AM »
Yeah, you're right--I took off the old and redid it and it worked first time and try as I might I couldn't break it.  Don't know what I did originally.  Thanks for the help and sorry to bother you.



Discussion & Troubleshooting / Re: invalid xml error
« on: August 01, 2006, 04:49:12 AM »
Hello Mr. V@no,

This is a test site to see if I could get your sitemap running in 1.73 because that's the thing that made me commit to 4images:

I was really supprised that the CAPTCHA thing is working--my php info say that GD Version is only(2.0.28 compatible)--the rss would be a bonus.



Discussion & Troubleshooting / invalid xml error
« on: August 01, 2006, 04:18:49 AM »
Wizz RSS News Reader running with Firefox gives me an "Invaid XML was retuned" error when I use it with my new install of 1.73.  In the Wizz help forum there was a reference to
which says that:

'utf8' codec can't decode byte 0xa9 in position 1151: unexpected code byte (maybe a high-bit character?)
 alert("? Copyright by Maui Tropica Gallery");
A common cause of this error is having a high-bit character (such as a curly quote or curly apostrophe) in your RSS feed. This can happen if you copy-and-paste a quote from another page that contains curly quotes. For maximum compatibility with readers, you should remove the invalid character or use a numeric entity equivalent.

You can also try changing your character encoding to a more liberal encoding. For example, if you have this at the top of your feed:

<?xml version="1.0" encoding="utf-8"?>

Try changing it to this:

<?xml version="1.0" encoding="iso-8859-1"?>

This can be a difficult error to diagnose, because the validator can not give you the exact location of the error. (This is due to a limitation of our parsing library; sorry, we tried very hard to work around it!) For example, if the validator says the error occurred at the end of a description element, the actual invalid character could be anywhere within the description.

XML parsing error: <unknown>:1:62: syntax error
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
The text of the error may contain additional helpful details. At a minimum, the actual line and column number where the error was detected will be reported.

The most common cause is encoding errors. There are several basic approaches to solving this: escaping problematic characters, escaping entire blocks of text with CDATA sections, or putting an encoding declaration at the start of the feed.

Another common error is the inclusion of whitespace characters (spaces, tabs, newlines) before the XML Declaration. If an XML Declaration is included, it must be the first thing in the document

Feeds should not be served with the "text/html" media typeExplanation
The web server is reporting an unexpected MIME type for a feed. Although we tried to parse it as a feed, aggregators may well report this as an error and act as if the user had pointed them at something other than a feed.

RSS feeds should be served as application/rss+xml (RSS 1.0 is an RDF format, so it may be served as application/rdf+xml instead). Atom feeds should use application/atom+xml. Alternatively, for compatibility with widely-deployed web browsers, any of these feeds can use one of the more general XML types - preferably application/xml.

Use the appropriate MIME type for your feed.

For static content served with Apache, use the AddType directive.
For static content served with Microsoft IIS, add a MIME type.
Other information can be found here or in the documentation provided by your server.

Any ideas how to fix this?

In the xml has a bunch of ?s highlighted red--for example(even though it's commented out):

Bitte beachten Sie, dass der folgende Copyrighthinweis
   auf JEDER Seite die von 4images ausgegeben wird sichtbar
   sein MUSS. Schriftart, Farbe etc. d?an die eigene
   Website angepasst werden, der Hinweis darf aber unter
   KEINEN Umst?en entfernt oder unsichtbar gemacht werden.
   Auch muss der Hyperlink zu intakt
   bleiben. Diese Bedingung ist Bestandteil der Lizenz dieser
   Software. Lesen Sie die Lizenz.txt Datei f?tere

and at the top this is highlighted in yellow:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">



Hello Mr. V@no,

Yes, yes, yes!! That was it! :mrgreen:

Thank you for the super fast response!

Now, after a little formatting, I'm ready for prime time.

As they say in the islands, "Mahalo Plenty!"



I have version 1.72 installed and was able to do all the tasks (I hope)  except installing the complete mod as suggested in step 13 but I did add the code for step 3 as instructed. Unfortunately things aren’t working, for instance, on the members profile the code:
{if user_lightbox}
               <td class="row1"><b>{lang_user_lightbox}</b></td>
               <td class="row1">{user_lightbox}</td>
{endif user_lightbox}

displays this in the source of the page

               <td class="row1"><b></b></td>
               <td class="row1"></td>
and on the light box page this code

{if url_lightbox_manage}
<a href="{url_lightbox_manage}"><b>{lang_lightbox_manage}</b></a>
{endif url_lightbox_manage}
only displays this:
<a href=""><b></b></a>

It was quite a haul and it would have been easy for me to make mistakes but even with so much tinkering there are no error messages popping up and in admin the 2 lines that refer to the number of light boxes and if multi lightboxs are allowed are there.

I bet I’ve done something dumb or missed something important.  I’ve already added the sitemap mod and am very happy with this whole environment and I realize people like me must frustrate the heck out the programmers who are so creative.  Thanks for the hard work!

Brian :D

Pages: 1 2 [3]