Login or create new account.

By registering on joomprod.com, you will have immediate access to all our free products and to the public side of our support forum.

Enjoy our subscriptions.

Each of our subscriptions allow you to enjoy the private side of the support forum and all the update of our products for a period ranging from 3 months to 1 year.

Payment And immediate download.

After subscribing to one of our subscription, the products are immediately downloadable.

Login

Or Register
Accueil / forum / Public Forum / Main Forum / [RESOLVED] Adsmanager view output

Support Availability Because we must sleep sometimes

Working days: Monday to Friday.
Reply time: Depending on the complexity of your support issue it's usually between a few hours to 48 hours.

Support is only guaranteed to paid subscribers

AdsManager - End of life

It is with great regrets that we have chosen to end the developpement of Adsmanager and its other associated components.

AdsManager is born 10 years ago and, as of today, the number of new subscriptions and downloads have fallen and we cannot maintain the component anymore.

All active subscribers will be able to continue enjoying support until the end of their subscription.

The components will be free and no support will be provided anymore for the other users.

×

Notice

The forum is in read only mode.

× OLD Forum post could be checked here : forum.joomprod.com

[RESOLVED] Adsmanager view output

More
11 years 7 months ago - 11 years 7 months ago #1057 by ades
[RESOLVED] Adsmanager view output was created by ades
In every view, although component outputs everything ok, whitespaces are added before first line of template file (tmpl/default.php).
After some hours, I found that these whitespaces are displayed while plugin cascade is included :
Example in list view :
* components/com_adsmanager/views/list/view.html.php l.231 => $plugins = $fieldmodel->getPlugins();
echoing before and after this line shows whitespace line
* administrator/components/com_adsmanager/models/field.php l.446
echoing before and after (displaying which plugin is included) show that only cascade plugin outs whitespaces.

Until now I haven't been able to find which part of images/com_adsmanager/plugins/cascade/plug.php is affected.

Thanks to work on it because templating when undisired space appears is difficult.
Last edit: 11 years 7 months ago by tompap.
The following user(s) said Thank You: discountchristi, adarr
More
11 years 7 months ago #1062 by tompap
Replied by tompap on topic Adsmanager view output
Yes, you are correct this is due to this plugin. a strange character is inserted but I was thinking to have fix this in 2.9.2 but the error reappear. Will recheck where the problem is. THe first time it was due to the header of this file "the comment" part
The following user(s) said Thank You: discountchristi, adarr
More
11 years 7 months ago #1118 by tompap
Replied by tompap on topic Adsmanager view output
I just retest this I don't see this problem anymore. Are you using the latest version ?
Do you have a link to see the bugs ?
The following user(s) said Thank You: discountchristi, adarr
More
11 years 7 months ago #1126 by ades
Replied by ades on topic Adsmanager view output
Hi,

Try with adsmanager included in silver pack, because in free version cascade plugin does not exists.

Joomla 3.1
Adsmanager 2.9.2
The following user(s) said Thank You: discountchristi, adarr
More
11 years 7 months ago #1133 by tompap
Replied by tompap on topic Adsmanager view output
Edit the images/com_adsmanager/plugins/cascade/plug.php
remove the first line
"<?php

And copy

?php just before /** on the same line.

Doing that, on demo.joomprod.com no more issue.

I don't understand where is this "strange characters but seems to be on the first line
The following user(s) said Thank You: discountchristi, adarr
More
11 years 7 months ago - 11 years 7 months ago #1134 by ades
Replied by ades on topic Adsmanager view output
Hi,

Thanks, I looked at file and found it is encoded in UTF-8 with BOM wich adds a " zero-width no-break space" byte at top of file.

When you convert file in UTF8 without BOM, then it seems to be OK.
Last edit: 11 years 7 months ago by ades.
The following user(s) said Thank You: adarr
Moderators: perry
Time to create page: 0.116 seconds
Powered by Kunena Forum