To use this website completely, it is necessary to store cookies on your computer.
 

* Navigator

Expand - Collapse

* Statistic


  • *Total Posts: 16431
  • *Total Topics: 2522
  • *Online Today: 7
  • *Most Online: 292
(12. Nov 2016, 09:37:31)
  • *Users: 1
  • *Guests: 0
  • *Spiders: 1
  • *Total: 2

* Calendar

Mo
Tu
We
Th
Fr
Sa
Su
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

PortaMx v0.990 and AEVA 1.4b compatibility issue

Started by b4pjoe, 19. Nov 2010, 01:27:38

previous topic - next topic

0 Members and 0 Guests are viewing this topic.

b4pjoe

19. Nov 2010, 01:27:38
I think there are at least three threads going about much of the same stuff.

Front page blank

PortaMx copyright

Output Buffer Problem PMX along with AEVA under RC4

I just want to give some more information after doing some more testing. I'm sure everyone is aware of the fix to comment out the line

Code Select
ob_start($obs && ($obs['name'] != 'default output handler') ? $obs['name'] : null);

from the 2 AEVA files aeva-subs.php and aeva-embed.php and then the white screen issue disappears in pages with embedded links. This is when the PortMx copyright disappears on those pages so I think those 2 issues are related.

I have tested AEVA 1.4b installed along with all 5 Portals that are available for SMF 2.0 RC4. SimplePortal, DREAM Portal, EzPortal, Adk Portal, and PortaMx. It works flawlessly with every portal except PortaMx...no white screens and no missing copyrights. I did not have to comment out the line of code above for any of the other portals. See attached images.









I'm not sure I would call it a bug but there is definitely an incompatibility between PortaMx and AEVA that I can't duplicate with other Portal software. I do not want to use another Portal software as I do believe that PortaMx is the best out there. Any thoughts on this Feline?

feline

#1
19. Nov 2010, 01:55:05
QuoteAny thoughts on this Feline?

No, currently not.
That is a bigger run to find out what's aeva do, and this I can't make in short time.
So I think, that will be fixed in the 1.0 ...

Fel
Many are stubborn in relation to the path, a few in relation to the target.

hartiberlin

#2
19. Nov 2010, 12:48:27
@b4pjoe,
please test it also with AEVA 2.04

Many thanks.

P.S: Did you already try the Mantis fix Feline posted
and the SQL settings variable ?

Do you also use SimpleSEF 1.1.1 with it ?

I don´t have any problems with embeded Youtube videos in AEVA 2.04.
Works okay for me.


Regards, Stefan.

b4pjoe

#3
19. Nov 2010, 18:58:06
I do not have AEVA 2.04 to test but you can test it simply enough. If your pages with embedded youtube links displays correctly then AEVA 2.04 does not have this problem. Also check those pages and see if the PortaMx copyright is displayed at the bottom of the page.

I do not use SimpleSef.

As far as I know there is no fix available yet.

b4pjoe

#4
19. Nov 2010, 20:19:16
I have done a little more testing...

We know that pages with embedded links display as white pages when PortaMx v0.990 is installed. We also know if we comment out the one line of code

Code Select
ob_start($obs && ($obs['name'] != 'default output handler') ? $obs['name'] : null);

from Aeva-Embed.php and Aeva-Subs.php that it fixes the white screen issue. Also, there is no white screen issue on the other 4 portals mentioned earlier but if we leave the line of code commented out and install the other 4 portals all of their copyrights disappear just like with PortaMx...except for EzPortal which places it's copyright above the SMF copyright. The other portals all place their copyright below the SMF copyright just like PortaMx and the Aeva Embedding copyright replaces their copyrights just like it does with the PortaMx copyright sooooo....
obviously the line line of code

Code Select
ob_start($obs && ($obs['name'] != 'default output handler') ? $obs['name'] : null);

is causing the white screen issue with PortaMx and the fix of commenting out that line of code in those two files causes the Aeva embedding copyright to replace any copyright directly below the SMF copyright instead of adding itself below that copyright as it does if that line of code is not commented out (Except that causes the white screen issue if PortaMx is installed).

b4pjoe

#5
22. Nov 2010, 17:33:07
OK....I think I have come up with some information that I hope is useful.

I have been using SMF 2.0 RC3 | PortaMx v0.980-1 | AEVA 1.3a on my live site for quite some time with no issues what so ever.

Moving to SMF 2.0 RC4 | PortaMx v0.990 (with patch applied) | AEVA 1.4b has caused the white screen issue on pages with embedded links.

So I went back and uninstalled AEVA 1.4b and installed AEVA 1.3a which works fine with PortaMx v0.980-1 and I have the white screen issue now using AEVA 1.3a that wasn't there when used with PortaMx v0.980-1. If I uninstall PortaMx v0.990 the white screen page issue disappears so I think it is safe to say that it is not caused by SMF 2.0 RC4 as the pages with embedded links display fine without PortaMx v0.990 installed on SMF 2.0 RC4.

BurakG

#6
22. Nov 2010, 20:21:34
I doubt any conclusion will help us as long as Fel is insisting PortaMx is perfect and refusing any possibility of an error..
Destiny. The design is clearly Ancient ..

http://www.mazdaclubtr.com
http://www.subaruclubtr.com

b4pjoe

#7
22. Nov 2010, 20:24:59
Unfortunately I believe you are right. :'(

feline

#8
22. Nov 2010, 21:25:09
Before you tell stories about me, read this:
http://theserverpages.com/php/manual/en/function.ob-start.php
Many are stubborn in relation to the path, a few in relation to the target.

b4pjoe

#9
22. Nov 2010, 21:30:06
No one is telling stories about you. And being as I'm not a programmer I understood nothing at all about that link..

Have you considered what I wrote that AEVA 1.3a works with PortaMx 0.980-1 and it doesn't with PortaMx v0.990?

feline

#10
22. Nov 2010, 21:35:20
I read all what you (and other) wrote.
But .. I don't have a aeva mod and i don't use videos from youtube or what else.
I hate viruses on my computers  :)
Many are stubborn in relation to the path, a few in relation to the target.

BurakG

#11
22. Nov 2010, 21:49:48
Quote from: feline on 22. Nov 2010, 21:35:20
I read all what you (and other) wrote.
But .. I don't have a aeva mod and i don't use videos from youtube or what else.
I hate viruses on my computers  :)


Aeva, youtube and viruses ? You should find  better excuses :)

I am sure it would take less than a minute of yours to install AEVA with PortaMX to a web site and understand what the problem is.
Destiny. The design is clearly Ancient ..

http://www.mazdaclubtr.com
http://www.subaruclubtr.com

b4pjoe

#12
22. Nov 2010, 22:54:49
Quote from: feline on 22. Nov 2010, 21:35:20
I read all what you (and other) wrote.
But .. I don't have a aeva mod and i don't use videos from youtube or what else.
I hate viruses on my computers  :)


I would be more than happy to do a clean install of SMF 2.0 RC4, PortaMx v0.990, and AEVA 1.4b on a test site and give you full forum admin and ftp access to it.

Autopilot

#13
22. Nov 2010, 23:11:38
Guys, the woman has obviously made up her mind and all the pleading in this world does not appear to have any affect on her. As she said, if we don't like, use something else.
She is right and the rest of the world is wrong. Simple.

Garry1953

#14
23. Nov 2010, 00:19:08
I've read all your comments and I'm amazed at some of the responses.

I have already posted a work around a day or two ago.

Copyright Work around

The problem seems to be Aveva uses an experimental function.
If you comment it out, Aveva works with PortaMX.

To get the Copyright to work correctly, you only need to amend Aveva, as I have done in the link above.

P.S. I edited it today, and added a link to the rogue function, so you can read it for yourselves.

Most importantly, everyone seems to forget that SMF is still in development mode, and we as users, are all very lucky to have talented programmers working on extensions, and giving away there many hours of work, for free.

I'm sure once SMF goes Gold, then all known bugs will be fixed by all parties concerned.