To me this is a bad idea. And for a very minor (almost non-) issue, IMO.javiexin wrote: Sun Jan 15, 2017 11:59 pm This I would consider a good working solution, with not much runtime impact (only a check every 5 to 10 minutes, or on demand...) and yet a very important reliability improvement (at least in my view).
Search found 676 matches
- Mon Jan 16, 2017 8:53 am
- Forum: [3.x] Tickets Discussion
- Topic: Potential bug in extension management
- Replies: 18
- Views: 46858
Re: Potential bug in extension management
- Mon Jan 16, 2017 8:51 am
- Forum: [3.x] Tickets Discussion
- Topic: Potential bug in extension management
- Replies: 18
- Views: 46858
Re: Potential bug in extension management
forget about this completely
This will be a moot point once the Extension manager will be able to download extensions autmatically from our database.
And this is a moot point since that is probably at least one, more likely two years out.
-javiexin
No, it already exists. It just hasn't ...
- Sun Jan 15, 2017 1:45 am
- Forum: [3.x] Tickets Discussion
- Topic: Potential bug in extension management
- Replies: 18
- Views: 46858
Re: Potential bug in extension management
This will be a moot point once the Extension manager will be able to download extensions autmatically from our database.
- Sat Jan 14, 2017 6:21 pm
- Forum: [3.x] Discussion
- Topic: [RFC][3.3.x] Supported PHP versions
- Replies: 31
- Views: 132500
Re: [RFC][3.3.x] Supported PHP versions
I voted 7.1, but I meant 7.0 
- Sat Jan 14, 2017 6:19 pm
- Forum: [3.x] Tickets Discussion
- Topic: Potential bug in extension management
- Replies: 18
- Views: 46858
Re: Potential bug in extension management
David is right. People should not delete active extension files from the filesystem, just as doing so to phpBB's core files would also result in unexpected results.
- Sun Dec 18, 2016 4:56 pm
- Forum: [3.x] Tickets Discussion
- Topic: PHPBB3-13803 / PHPBB3-13891 - Reparsing text
- Replies: 65
- Views: 180555
Re: PHPBB3-13803 / PHPBB3-13891 - Reparsing text
I think that the correct way to do it would be a big overhaul of message_parser and the generate_text_for_* functions into a unified API that supports some sort of contextual configuration that would allow the text to be treated differently depending on whether it's from a post, a signature, etc ...
- Thu Dec 15, 2016 5:37 pm
- Forum: [3.x] Discussion
- Topic: 3.2 sample config file
- Replies: 8
- Views: 22332
Re: 3.2 sample config file
Our config's may look different than yours for several reasons. Aside from the obvious database credentials, we could end up with different cache types, debug definitions and environments (production, development, etc).
That's why, if you would have installed a vanilla board, you would see what ...
That's why, if you would have installed a vanilla board, you would see what ...
- Wed Dec 14, 2016 7:49 pm
- Forum: [3.x] Discussion
- Topic: 3.2 sample config file
- Replies: 8
- Views: 22332
Re: 3.2 sample config file
Why don't you install a new board and compare it with that?
- Sun Nov 27, 2016 7:55 pm
- Forum: [3.x] Discussion
- Topic: EVENT Bug: Jumpbox bug if you use EVENT overall_footer_content_after.html
- Replies: 9
- Views: 29830
Re: EVENT Bug: Jumpbox bug if you use EVENT overall_footer_content_after.html
Adding the clear class breaks the existing layout of your div and you need to add extra css code to get it back to normal.
People that add content in the event usually want it to show in the main page footer, less on these pages: Memberlist, The team, Viewing Profiles, Vieving Groups.
Seems odd ...
- Sat Nov 26, 2016 9:41 am
- Forum: [3.x] Discussion
- Topic: EVENT Bug: Jumpbox bug if you use EVENT overall_footer_content_after.html
- Replies: 9
- Views: 29830
Re: EVENT Bug: Jumpbox bug if you use EVENT overall_footer_content_after.html
The event is perfectly fine...and correct!
There are floated elements in the style. Your template event listener needs to clear floats. Just add class="clear" to your div.
There are floated elements in the style. Your template event listener needs to clear floats. Just add class="clear" to your div.