Page 6 of 10

Re: Incompatible Extensions for 3.2

Posted: Wed Jan 25, 2017 8:47 am
by david63
«THÖMÅS®©» wrote:
Wed Jan 25, 2017 3:03 am
Will any of these be updated for 3.2 or will there be similar mods that have the same functions made?
You will have to ask the original extension developer and/or keep a lookout at what is being posted in the Extensions in Development forum

Re: Incompatible Extensions for 3.2

Posted: Wed Jan 25, 2017 11:02 am
by 2600
NorthWoodMediaWorks wrote:
Tue Jan 24, 2017 9:58 pm
Anyone else think a sticky topic like this for Styles in 3.2 might fly? Just sayin'

Cheers :)
:lol: I'm pretty sure that would include every style that was built during 3.1. ;)

Re: Incompatible Extensions for 3.2

Posted: Wed Jan 25, 2017 2:41 pm
by NorthWoodMediaWorks
John connor wrote:
Wed Jan 25, 2017 11:02 am
NorthWoodMediaWorks wrote:
Tue Jan 24, 2017 9:58 pm
Anyone else think a sticky topic like this for Styles in 3.2 might fly? Just sayin'

Cheers :)
:lol: I'm pretty sure that would include every style that was built during 3.1. ;)
I am seeing different levels of compatibility between certain styles. My main board uses a modded We_Universal, and on my 3.2 test board, it seems to be completely functional... I have yet to find a glitch. Black, on the other hand, has some icon issues. But that, as you have pointed out, is to be expected.

Re: Incompatible Extensions for 3.2

Posted: Wed Jan 25, 2017 6:11 pm
by Mick
Please stick to topic.

Re: Incompatible Extensions for 3.2

Posted: Thu Jan 26, 2017 1:20 pm
by Aros010
inuyaksa wrote:
Sun Jan 22, 2017 8:45 pm
Fixed @mention system for 3.2 at https://github.com/inuyaksa/mentions
Working fine!! Thank you!

Re: Incompatible Extensions for 3.2

Posted: Wed Feb 01, 2017 2:13 am
by buksida
Can anyone confirm if Tapatalk works with version 3.2?

Re: Incompatible Extensions for 3.2

Posted: Wed Feb 01, 2017 7:30 am
by janus_zonstraal
Yes there latest version is working.

Re: Incompatible Extensions for 3.2

Posted: Wed Feb 01, 2017 8:02 am
by Nully
buksida wrote:
Wed Feb 01, 2017 2:13 am
Can anyone confirm if Tapatalk works with version 3.2?
Yes it works.

Re: Incompatible Extensions for 3.2

Posted: Wed Feb 01, 2017 9:41 pm
by Scanialady
@david63: user login redirect 2.1.0 (Github) causes sql errors for me if I want to login to ACP (upgraded from 3.1.9 to 3.2.0, test board). I have to go back, than I can go to ACP.

Code: Select all

Allgemeiner Fehler
SQL ERROR [ mysqli ]

Unknown column 'POST_ANNOUNCE' in 'where clause' [1054]

SQL

SELECT topic_id, topic_time FROM phpbb_topics WHERE topic_type = POST_ANNOUNCE ORDER BY topic_time DESC LIMIT 1

BACKTRACE

FILE: (not given by php)
LINE: (not given by php)
CALL: msg_handler()

FILE: [ROOT]/phpbb/db/driver/driver.php
LINE: 999
CALL: trigger_error()

FILE: [ROOT]/phpbb/db/driver/mysqli.php
LINE: 193
CALL: phpbb\db\driver\driver->sql_error()

FILE: [ROOT]/phpbb/db/driver/mysql_base.php
LINE: 45
CALL: phpbb\db\driver\mysqli->sql_query()

FILE: [ROOT]/phpbb/db/driver/driver.php
LINE: 270
CALL: phpbb\db\driver\mysql_base->_sql_query_limit()

FILE: [ROOT]/phpbb/db/driver/factory.php
LINE: 321
CALL: phpbb\db\driver\driver->sql_query_limit()

FILE: [ROOT]/ext/david63/loginredirect/event/listener.php
LINE: 155
CALL: phpbb\db\driver\factory->sql_query_limit()

FILE: (not given by php)
LINE: (not given by php)
CALL: david63\loginredirect\event\listener->login_redirect()

FILE: [ROOT]/vendor/symfony/event-dispatcher/EventDispatcher.php
LINE: 184
CALL: call_user_func()

FILE: [ROOT]/vendor/symfony/event-dispatcher/EventDispatcher.php
LINE: 46
CALL: Symfony\Component\EventDispatcher\EventDispatcher->doDispatch()

FILE: [ROOT]/phpbb/event/dispatcher.php
LINE: 60
CALL: Symfony\Component\EventDispatcher\EventDispatcher->dispatch()

FILE: [ROOT]/phpbb/event/dispatcher.php
LINE: 46
CALL: phpbb\event\dispatcher->dispatch()

FILE: [ROOT]/includes/functions.php
LINE: 2350
CALL: phpbb\event\dispatcher->trigger_event()

FILE: [ROOT]/adm/index.php
LINE: 37
CALL: login_box()
Someone has written a suggestion to change the files on the support section of CDB - I will try.

Re: Incompatible Extensions for 3.2

Posted: Wed Feb 01, 2017 10:45 pm
by Mick
Scanialady wrote:
Wed Feb 01, 2017 9:41 pm
@david63: user login redirect 2.1.0 (Github) causes sql errors for me
You should seek support for the extension in the link you provided.

Re: Incompatible Extensions for 3.2

Posted: Thu Feb 02, 2017 8:07 pm
by Scanialady
Scanialady wrote:
Wed Feb 01, 2017 9:41 pm
...

Someone has written a suggestion to change the files on the support section of CDB - I will try.
As you can see: I have done ;) - my post was an info that this 2.1 tree does not work.

The linked fix works for me - but you need to clear the database manually (info, too)

So we can say: there is not a working version of user login redirect for 3.2.0 - the Github 3.2.x tree does not work.

Re: Incompatible Extensions for 3.2

Posted: Thu Feb 02, 2017 9:17 pm
by david63
Scanialady wrote:
Thu Feb 02, 2017 8:07 pm
the Github 3.2.x tree does not work
If you take random code from Github that has not been released then there is no guarantee that it will work. I will get around to looking at it when I get time - along with another 20+ extensions.

Re: Incompatible Extensions for 3.2

Posted: Fri Feb 24, 2017 12:08 am
by milango
Recent Topics: Not work.

Re: Incompatible Extensions for 3.2

Posted: Fri Feb 24, 2017 7:00 am
by janus_zonstraal
milango wrote:
Fri Feb 24, 2017 12:08 am
Recent Topics: Not work.
This one do https://github.com/Sajaki/RecentTopics/ ... /2.2.0-RC2

Re: Incompatible Extensions for 3.2

Posted: Fri Feb 24, 2017 11:37 am
by milango
janus_zonstraal wrote:
Fri Feb 24, 2017 7:00 am
milango wrote:
Fri Feb 24, 2017 12:08 am
Recent Topics: Not work.
This one do https://github.com/Sajaki/RecentTopics/ ... /2.2.0-RC2

Hei. How to setup?
I upload to /ext/sajaki/recenttopics/

But I do not see in ACP.
HELP ME