Since I am using your software for validating our pages, these pages no longer validates...
Daniel.
Can you tell me few examples of such links? In most links these &-amp; combinations should be converted to & symbols. Perhaps there are some rare examples where this conversion should not be done.
Thank you!
Best regards,
Oleg Chernavin
MP Staff
I am talking of any link passing more than one parameter. We are coding them with &-amp; for page validation purposes.
Here is an example: http://www.cio-dpi.gc.ca/cio-dpi/index_e.asp.
When this page is downloaded the &-amp; in links are being replace with &, which no longer validates.
Daniel.
Can you tell me, what kind of problem do you experience?
Oleg.
I am running page validation in batch mode on the files downloaded with OEP.
Looking at the page source, the &-amp; are converted to an &, in links with multiple parameters, on the pages downloaded with OEP.
I am wondering, if the original page source had links coded with &-amp;, can the downloaded page source of OEP have them?
Daniel.
Oleg.
I can wait a month.
In the meantime, I have look at a previous web site download and notice OEP use to put the &-amp; in links. Something must have change with the newer releases.
Daniel.
Oleg.
Is this request still on your todo list?
Thanks.
Daniel.
I reviewed the source code related to the links change when translating them offline. It looks like it will be quite hard to make &-amp; symbols preserved. At least, in the cases when some symbols in URLs are & and others - &-amp;.
If it is really important, I can add an option to change all & symbols in offline links to &-amp; - even those which were not coded this way online. It should work for this site.
Oleg.
since I am trying to find where in links the &-amp; are coded as &.
OEP 2.9 used to keep the &-amp within an offline or online link on the dowloaded page source.
Daniel.
Oleg.
I wonder if you could have another look at this.
thanks.
Daniel.
Thank you!
Oleg.
When EXPORTING a project with the KeepAMP, I notice the following:
From this page
http://www.expenditurereview-examendesdepenses.gc.ca/as-se-fra.asp
The link under the Recherche black button is keeping the & characters but
the second link in the sidebar are being removed while exporting.
It seems that if the href contains the "http://" characters then the amp; characters are kept, but if it's a relative link like the one for the sidebar, they are being removed.
Can you have another look.
Thanks.
Daniel.
Oleg.
Danie.
http://www.metaproducts.com/download/betas/OEP3720.zip
Oleg.
I tried the updated version on a small site and it's working on the downloaded files as well as on the exported files.
Thanks again.
Daniel.
Oleg.
I just notice that when using the KeepAMP as a command parameter, the exported pages will keep the amp; but the actual link that contains them, will no longer get the .htm appended to them, for a downloaded page.
I can send you directly a link to a small web site for testing.
Daniel
Oleg.
I have received and tested the newer version you sent me, and it's working.
Thanks again for your great support.
Daniel.
Oleg.
I now notice that if the URL with a query string is longer than about 175 characters, the downloaded pages gets truncated and appended with a series of 10 characters or digits.
This can be tested with the same domain I forward you before.
Can you have a look.
Thanks.
Daniel.
Yes, this is normal. Windows doesn't allow to create very long filenames. So, Offline Explorer truncates them and adds a unique code to make sure the truncated links are different.
This feature exists for many years in Offline Explorer.
Oleg.
It seems the link within the project page are having a different unique code for those long URL's.
Possibly cause by the extra "amp;" characters in the URL itself.
Daniel.
http://www.metaproducts.com/download/betas/OEP3767.zip
Thank you!
Oleg.
Thanks again.
Daniel.
Oleg.
I notice the following:
A page would download without being recoded with a unique code when it's filename would be short enough. But then when it is a linked page that contains the amp; then the linked will get recoded with a unique code, which would make it unbrowsable.
I was able to reproduce this behavior on the same web site you are using for testing this.
Can you have a look.
Thanks.
Daniel.
http://www.metaproducts.com/download/betas/OEP3769.zip
Oleg.
I have found other issues but I wonder if they are created with the way our application works.
I will keep you posted.
Daniel.
Oleg.