Odd PDL Button Behaviour

[tapiochre]

Hi

Joomla 1.5.23
PhocaDL 1.3.9
PhocaDL Plugin 1.3.6
PhocaDL Button Plugin 1.3.5

An odd thing is happening with source code to download PDF files on an article page.

The code on the page (during Admin editing in the backend) is:

Code: Select all

<p>{phocadownload view=file|id=13|text=How children are taught|target=b}</p>
<p>{phocadownload view=file|id=12|text=How we teach Numeracy|target=b}</p>

But this is what is rendered in the browser for that page:

Code: Select all

<p><div class="phocadownloadfile64"><a href="/index.php/other-letters-home?download=13%3Ahow-children-are-taught-in-foundation-class-" target="_blank" >How children are taught</a></div></p>
<p><div class="phocadownloadfile64"><a href="/index.php/component/phocadownload/category/8-carer-help?download=12%3Asample" target="_blank" >How we teach Numeracy</a></div></p>

So I am really puzzled why the first is correctly rendered as a request for the file, while the second entry is incorrectly rendered.

I'm looking for help as I have tried various changes to the code (swapping the file ID, checking the file name for spaces etc) but all to no avail.

Both files are simple PDFs, both in the same joomla folder, both in the same category (the prob exists also if I change the category).

I did find that if I associate a file with a Category ID >= 8, then the fail happens. The inverse is true: set the category for a file to <=7 and it downloads fine.

It also happens if I copy/paste the code to a new webpage article or if I recreate the links using the button in the editor.

Can anyone suggest if I am making an error here?

Chris

[Jan]

Hi, really no idea what can be wrong there, the first link takes SEF and the second not. Testing now on my server without any problem ????

In case none of the link will be converted to SEF, then this happened.
https://www.phoca.cz/documents/16-joomla ... -in-joomla
But in this case really no idea what can be wrong there?

[tapiochre]

Thanks for the feedback Jan

I am even more confused because, having left the site alone for 24 hours or so, the problem described in my posting has "self resolved". In other words, the problem no longer exists. I haven;t emptied any caches or even powered off the client, so something was odd, but for now, I'll close this posting and monitor it!

Thanks anyway!

Chris

[Jan]

Ok