- This topic has 2 replies, 3 voices, and was last updated 10 years, 8 months ago by
.
-
Posts
-
Hi,
I’m a WP (and web programming) newby, so please forgive me if I’ve missed something obvious. Here is my observation, then the details.
I use [weaver_popup_link] around some text [/weaver_popup_link] to open a popup window and it works perfectly well. I use the exact same statement around an <img src=”file name.jpg” /> image with a file name with spaces, and it works perfectly well. I use the exact same statement around an <img src=”file_name.jpg” /> image without a space, and the width of the popup window turns full screen.So here are some details:
This one works:
[weaver_popup_link href='http://my-weaver-page/' h='500' w='500' scrollbars=false]My Text[/weaver_popup_link]This one works too:
<td>[weaver_popup_link href='http://my-weaver-page/' h='500' w='500' scrollbars=false]<img src=”http://my-domain/wp-content/uploads/Logos/Logo Name.jpg” alt=”Logo Name” align=”middle”/>[/weaver_popup_link]</td>I should probably mention here that I did not use the media uploader for the image, but uploaded it directly via ftp, otherwise the spaces in the filename would have been replaced with hyphens by WP. I also tried the route via media upload from WP, but to no avail. As the spaces in the filename get replaced, the result is the same as for the directly uploaded image with no spaces in the filename.
So here is the version where the width of the popup window spans over the whole width of the screen (note that the only difference is the missing space in the file name, and yes, both files exist):
[weaver_popup_link href='http://my-weaver-page/' h='500'
w='500' scrollbars=false]<img
src=”http://my-domain/wp-content/uploads/Logos/LogoName.jpg” alt=”Logo
Name” align=”middle”/>[/weaver_popup_link]So, I looked at the actual code generated. The correctly working one, with the spaces in the file name, created the following code:
<a onclick=”window.open(this.href,’_blank’,’toolbar=no,location=no,directories=no,status=no,scrollbars=1,resizable=no,
menubar=no, width=500,height=500′);return(false)“ href=”http://my-weaver-page/“><img align=”middle“ alt=”Logo Name“ src=”http://my-domain/wp-content/uploads/Logos/Logo Name.jpg“>The non working version, with no spaces in the file name, gave the following code:
<a onclick=”window.open(this.href,’_blank’,’toolbar=no,location=no,directories=no,status=no,scrollbars=1,resizable=no,
menubar=no, ,height=500′);return(false)“ href=”http://my-weaver-page/“><img width=”120“ height=”37“ align=”middle“ alt=”Logo Name“ src=”http://i0.wp.com/my-domain/wp-content/uploads/Logos/LogoName.jpg?w=960“>So for whatever reason the width argument for the window.open() got omitted. Additionally, the file seems to have been uploaded to wordpress.com. As I said, I’m new to WP, so I haven’t quite figured out the complete architecture of it yet and frankly don’t know what gets uploaded and what not. Additionally to the changed source, there is now this weird URL parameter ?w=960. The image has exactly 120×37 pixels, as also stated in the parameters of the image.
I can’t really tell where the problem lies, either with the combination of the popup code and the upload of the image, with the upload of the image and the URL parameter, or simply with the popup short code. But if the result is dependent on whether there is or is not a space in a file name sounds rather fishy too me. I would appreciate any help on this topic.
If you are new at this., then you should be using the latest weaver theme which is Weaver Xtreme.Weaver II (pro) is end of life, and will only get major bug fixes for wordpress compatibility.If the shortcode has a problem with certain file names, it is unlikely it will get fixed so you would have to use working naming, but @weaver can confirm.
- The forum ‘ Weaver II Pro’ is closed to new topics and replies.