nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

LSCS/LSDS .page submit

SameerBoodhoo

Hi,

I have a component in which i have a form whose type is set to "external".

<form type="external" ....>...</form>

I am submitting the form using Javascript after setting my parameters in the $SUBMIT_URL.

Everything works correctly in Teamsite, the pagination and filters also.

When the .page is deployed to PROD and on submitting, "submit=true&componentID=xxxx" is appended to the url which is causing the page just to refresh and not getting new values from the db.

When i manually remove the two parameters stated above, i get new values from DB.

Could you please help me in understanding this issue and possibly how to solve it.

Thank you a lot.

Find more posts tagged with

Comments

Rick Poulin

I'm not sure I follow your example.. Can you post examples of the full URL that works and that doesn't?

SameerBoodhoo

Hi,

Okay i will try to be more clearer.

For the prod, as an example with parameters:

http://domain-name/sites/mypage.page?submit=true&componentID=xxxx&page=2

For Teamsite, we have usual url when previewing the .page, we get only

http://domain-name/../mypage.page?page=2

I do not understand why in Standard Teamsite/Livesite, everything is working correctly. But in the prod server, the same page

http://domain-name/sites/mypage.page?submit=true&componentID=xxxx&page=2

is just like a page refresh.

Note that the DB procedures and Java codes have been double checked.

Rick Poulin

I still don't understand what you mean.. if you submit a form, it should trigger a full page refresh on either side.

The only difference would be if you have code that instead takes the form values and posts via AJAX. If that's the case, maybe your Javascript has made assumptions on the authoring side that don't hold true on the runtime.

It's still a bit hard to diagnose, because I don't understand the flow you're trying to describe, or what your code is attempting to do. Maybe answer this -- what is the difference between the current behaviour on the runtime versus what you want to happen on the runtime?

SameerBoodhoo

Hi,

I hope this time i can be much clearer,

In the component, there is something like this:

function paginate(pageNumber){

	    document.getElementById('myForm').action='$SUBMIT_URL[pageNumber='+pageNumber+']';
	    var result = document.getElementById('myForm').submit();
}

<form type="external" method="POST" id="myForm">

	//some text and display

</form>

<ul><li> //pagination links whose href is linked to the function paginate </li></ul>

This component is placed in a page and is previewed in Teamsite.
The url is: http://domain-name/iw-cc/command/iw.group.preview_file?vpath=//hostname/default/main/branch/subbranch/WORKAREA/workarea/sites/mysite/mypage.page

This page is supposed to get the 10 records from db. When i clicked on page number 2, the page refreshes but the url remains the same and i get the next 10 records from DB.

The .page is deployed to LSCS, the url is http://domain-name/mysite/mypage.page. Here, i get my first 10 records on the first page load. However, when i click on page number 2, the url changes to

http://domain-name/mysite/mypage.page?submit=true&componentID=1416214893755&pageNumber=2 and the data remains the same (first 10 records from DB) which should not be the case.

If i remove the "submit=true&componentID=1416214893755" leaving the url like this : http://domain-name/mysite/mypage.page?pageNumber=2, i get the correct data. (that is the next 10 records form DB).

I hope that i have been much clearer about this scenario. Could it be a livesite configuration on LSCS/LSDS?

Rick Poulin

Ok, got it.

You have two issues. The first is that you didn't notice, but the URL on the preview side changed too. The difference is that the content appears in an iframe, and the URL of the iframe changed when you submitted the form even though the top-level frame (the one with the SitePublisher toolbar) didn't. If you want this kind of functionality, you're going to have to use AJAX to avoid a page refresh.

On the runtime, the reason your content isn't reacting to the new parameter is because your component cache is probably set something other than "Do Not Cache". You cannot use the LiveSite cache for components that are dynamic in this way because it caches the final state of the output, and the query string parameters aren't part of the cache key. If you want performance optimization via caching for this, you'll have to write it in your external or somewhere within your Java code.

SameerBoodhoo

Hi,

So basically, i need to set the cache to "Do not cache" and then redeploy my page to the PROD server?

Could you please be more explicit about the performance optimization via caching?

Thank you.

Rick Poulin

Yep, that's what you need to do.

What I'm suggesting is that if you find that the performance of this component is too poor, you'd have to implement your own caching in the datasource for the component rather than the final output. What that means is your component connects to a Java class right? Write some code in that class to persist the data for longer than just the current request.

This is not trivial and is difficult to do correctly if you don't know what you're doing, so I'd suggest talking to an experienced Java developer if you're not comfortable with this topic. I just went to Google and found the first tutorial that seems on topic, but I wouldn't suggest just copy+pasting this into your codebase -- there's more thinking required than that.

SameerBoodhoo

Yes, the component connects to my Java class. However, i do not want persist the data longer. I will try to set the "Do not cache" option and re-update my templates, .pages and redeploy using the Publish Livesite workflow.

By the way, is there any sort of configuration that can be done on LSDS for disabling the caching? I do not have much info about the application server, it is Weblogic i think.

Thank you.

Rick Poulin

SameerBoodhoo wrote:
By the way, is there any sort of configuration that can be done on LSDS for disabling the caching? I do not have much info about the application server, it is Weblogic i think.

Yes, but you generally don't want to turn it off for the whole implementation. Most of your components can continue to cache the output, when they don't change depending on the incoming request. Caching is a good thing, even if it got in the way of this particular scenario.

SameerBoodhoo

Okay. I could test the first option. If this does not work, i will ask them to disable the cache for some verification.

I will update here as soon as possible.

Thank you a lot. Smiley Happy