Westminster New

[DivaVocals]

I know I have a lousy track record, but isn't that obvious! My point was that is not standard procedure and not that easy to figure out - one would assume comments are fairly safe! So if this helps someone - ok; one peculiarity on display - the forum is here for that purpose, isn't it!?

what wasn't obvious was the fact that you were sharing info vs asking a question.. so no.. the post I responded to wasn't all that OBVIOUS.. IJS..

Not "standard procedure".. ummmmm... okay.. perhaps not for you, but the //, is not STANDARD for comments in CSS or HTML documents at all (like NEVER).. what comment code is used depends on many factors, but it isn't always //..

[picaflor-azul]

Your a gem thank you so much Anne

I had been looking at that for hours and trying different combinations but totally didnt think to add the code for top wrap to my css. WOHOOO now this is looking as I wanted thank you again - your the best!!

No problem ;) I don't mind helping people out when they have made an effort to figure things out for themselves and done some legwork and are just stuck on something. It is a little frustrating when people just want you to tell them the answer without any work themselves. I can tell that you have spent a good amount of time working on the template, customizing it to your needs ;)

Thanks,

Anne

[DivaVocals]

No problem ;) I don't mind helping people out when they have made an effort to figure things out for themselves and done some legwork and are just stuck on something. It is a little frustrating when people just want you to tell them the answer without any work themselves.

**nods in agreement**

[DivaVocals]

I know I have a lousy track record, but isn't that obvious! My point was that is not standard procedure and not that easy to figure out - one would assume comments are fairly safe! So if this helps someone - ok; one peculiarity on display - the forum is here for that purpose, isn't it!?

and since we're SHARING so that folks KNOW, here's MORE on comments. (because Google is your friend..)

How do I insert comments in JavaScript code? Answer: JavaScript supports three different types of comments:

1. Multiple-line C-style comments. Everything between [FONT=Courier New,Courier]/*[/FONT] and [FONT=Courier New,Courier]*/[/FONT] is a comment, for example:
   [FONT=Courier New,Courier]/* This is a comment */ /* C-style comments can span as many lines as you like, as shown in this example */ [/FONT]
2. One-line comments of C++ style. These comments begin with [FONT=Courier New,Courier]//[/FONT] and continue up to the next line break:
   [FONT=Courier New,Courier]// This is a one-line comment [/FONT]
3. One-line comments with the HTML comment-opening sequence ([FONT=Courier New,Courier]<!--[/FONT]). Note that the JavaScript interpreter ignores the closing characters of HTML comments ([FONT=Courier New,Courier]-->[/FONT]). Consider this example:
   [FONT=Courier New,Courier]<!-- This is treated as a one-line JS comment <!-- It works just like a comment beginning with // <!-- --> This is also a one-line JS comment <!-- --> because JS ignores the closing characters <!-- --> of HTML-style comments [/FONT]

Multiple-line C-style comments - Also supported in *.php, & *.css files
One-line comments of C++ style - Also supported in *.php files
One-line comments with the HTML comment-opening sequence - Also supported in *.html files

There is no ONE "STANDARD Procedure" for comments. There are a few different options.. Which style you use depends very much upon the kind of file/code you are using it in..

[missesbeehaven]

Hi Anne,

While doing a little more work on my zen store and your awesome template I found what may be a little bug typo just maybe or it appears that way to me.

on my contact us page I was seing my address listed twice once before the actual contact us header and form and then again down lower in the page just before the contact form fields.

When i looked into /includes/templates/westminster_new/templates/tpl_contact_us_default.php

I discovered a duplicate entry of the following code which when I removed the code from line 20 to 22 the duplicate address was corrected:

<?php if (CONTACT_US_STORE_NAME_ADDRESS== '1') { ?>
<address><?php echo nl2br(STORE_NAME_ADDRESS); ?></address>
<?php } ?>

Just posting here in case it is a bug and if others are looking for the same problem / solution.

[kalastaja]

Multiple-line C-style comments - Also supported in *.php, & *.css files
One-line comments of C++ style - Also supported in *.php files
One-line comments with the HTML comment-opening sequence - Also supported in *.html files

Ok, point taken.
BTW: (maybe a general question, but since we're on the subject) Why doesn't //xxxx ?> brake the php code?

[DivaVocals]

Ok, point taken.
BTW: (maybe a general question, but since we're on the subject) Why doesn't //xxxx ?> brake the php code?

If you want to have an in depth discussion on the use of comments in programming, or any other topic NOT RELATED to the support of this template, start a NEW topic on it..

[kalastaja]

Choosing an item from the shop generates:

in Finnish: http://www.dtc.fi/index.php?main_page=product_info&cPath=3
in English: http://www.dtc.fi/index.php?main_page=product_info&cPath=3&products_id=10

The Finnish call ends up as a blank page. The English work as expected.
BTW. Traveling category handles only cPath, no products_id without backfiring .

[kalastaja]

Log entries - pointing towards fi_fi:

[03-Feb-2015 16:19:06 Europe/Helsinki] PHP Warning:  Cannot modify header information - headers already sent by (output started at /home/etm99gtn/public_html/includes/languages/fi_fi.php:1) in /home/etm99gtn/public_html/includes/init_includes/init_templates.php on line 78
[03-Feb-2015 16:19:06 Europe/Helsinki] PHP Warning:  Cannot modify header information - headers already sent by (output started at /home/etm99gtn/public_html/includes/languages/fi_fi.php:1) in /home/etm99gtn/public_html/includes/functions/functions_general.php on line 46

[Ajeh]

Based on the error message, check the file:
/home/etm99gtn/public_html/includes/languages/fi_fi.php

and remove the space(s) blank and/or line(s) at the start of the file before the opening php bracket <?php and see if this corrects the problem ...

As a precaution, check at the bottom of the file and if there is a closing php bracket ?> remove that as well ...