3942016

NetSuite support for integrate PayPal Express Checkout will be enabled on 10/9. We are finalizing testing of the feature and will be roling it out completely and fully tested on that date. We thank you for your patience and we apologize for any misunderstanding about the release date for that feature.

If the customer clicks PayPal Express Checkout from the shopping cart, they can use express checkout, bypassing login/registration. If the customer has already logged in and gotten to the checkout seqence, they can still choose Paypal Express Checkout by choosing PayPal from the payments method page (returning customers…

Looks to be a legitimate issue. Please contact support and file a case, this should be looked at by development.

Wait... is the document's file set to "available online" = T?

that probably shouldn't be happening. Can you paste the script here that A_TAG_THAT_CONTAINS_SCRIPT should correctly evaluate to? There may be a workaround available.

Is there a case or defect filed for this? Please identify because I think this may be an injection, and I want to 1) find a workaround and 2) get it fixed safely ASAP

Please file a case, and have support attach your case to issue 179378, which adds weight to the defect. It looks like one NetSuite should try to get addressed pretty quickly.

It's required to forward declare any tags you might be referencing from your template that would be "uncovered" because the tags come from the text which is the result of evaluating other tags. For example, you have an item custom field with some HTML in it, and within that HTML there are references to tags. You would have…

There is no "current" event in a Web store context (only a current item, sitecategory and customer). If you have the numeric id of a specific event, you could access it using <%=getAttribute("event", <id>, "location")%>

This is tracked by issue 155614, which is being addressed with high priority.

Please file a case with NetSuite support. Please give them the URL in your Web site which demonstrates the problem (the URL you start at where you have to click home again).

<%=getCurrentAttribute('request','scheme')%> Make an URL like this: <%=getCurrentAttribute('request','scheme')%>://www.theurl.com

In your add to cart scripts: <a href="javascript: document.myform1.submit(); try taking out the space between "javascript:" and "document." in other words, correct them to look like <a href="javascript:document.myform1.submit();

Issue 154452 has been filed to track this problem. If you haven't already, please file a case with support referencing this issue number.

Have you tried using these tags from your hosted page? For an item's HTML: <%=getAttribute('item', <id>, 'storepagehtml')%> For a category's HTML: <%=getAttribute('sitecategory', <id>, 'storepagehtml')%> For <id>, pass in the fixed id of the item or category you'd like displayed. Note that for this HTML's embedded…

Did you try checking this check box? Set up Web Site > Shopping > Shopping Basics > Require Login For Pricing

Two additional issues have been filed: - If PayPal is the only available payment method available, skip the payment method page (issues 135700 and 90735) - Add ability for checkout to require shipping address but not require a shipping method (issue 135702)

sterry, Please file a case for the 'PO Rate' field not getting populated on orders generated from the Web store, and post the case number here. Thanks, - DJ

This is being tracked by issue 131051

You can tell which tab you are in from within the HTML of <NLPAGETABS> by referencing the following tabs, which return unique values for each tab: <NLTABID> - Resolves to a number that uniquely identifies the tab <NLTABLABEL> - Resolves to the label of the tab <NLTABLINKURL> - Resolves to the tab's URL <NLTABLINKATTRIBS> -…

Attribute tags are substituted on the server, not the client. They are substituted before the page ever gets to the browser. So all parameters must be static. Your formula field idea ought to work, but I haven't tried that yet.

Until we can release the capability to make information items non-searchable, you can use this workaround to hide the error messages: Go to Set up Web Site > Customize Text > Error Messages, scroll to the bottom, and change: [Error processing dynamic tag {1} : {2}] to <!--Error processing dynamic tag {1} : {2}--> That will…

Issue 128170 is a request to add a preference that controls whether information items appear in search results. This was implemented and will be released tomorrow (Wednesday) night to everyone on version 2007.

High priority issue 128170 has been filed, tracking this issue.

Two possibilities: - Do you have display of site navigation portlets disabled under Set up Web Site? - The site navigation portlet tag is currently not supported from the Welcome tab.

When the first post was made, internalid was not properly supported. As of the most recent version of NetSuite, 'internalid' is fully supported for all record types. With tag substitution, internalid is now the preferred way to obtain the id of any record. Can you check to see if you get the expected result (1666) using…

I sent a note to our documentation group. Thanks for the heads-up.

What is the URL of your non-working form page? The URL in post #1 doesn't work, it is corrupted.

Hosted pages that use the <NLPAGETABS> tag will display all the web site's tabs. Whichever tab was last hilited before navigating to the hosted page will continue to be hilited as you view hosted pages. There is currently no other way to specify that a particular tab be hilited from a hosted page, it just stays under the…

Standalone online forms do not support Web store tags. Instead, you can publish the online form using an "online form information item" and then the page will be a true Web store page, supporting all tags and templates.