Category: Less than 30-minutes fix
The task should not take more than 30 minutes to be solved. Tag a bug or wish with this category in order to have them easily filtered at a TikiFest for example.
Show subcategories objects
| Name | Type |
|---|---|
| PHP 7.4 errors in tiki-Wiki 21.x | tracker item |
|
PHP warning by lib/setup/javascript.php
{CODE(Colors="Tiki")} NOTICE (E_NOTICE): Undefined index: mobile_mode At line 208 in lib/setup/javascript.php {CODE} Is constantly shown (to admin only). I have never used the mobile mode... |
tracker item |
|
Please add info for admins regarding Google analytics
{syntax type="tiki" editor="plain"} Tiki has the option to interact with Google Analytics. Now the first court rulings are there: Google Analytics directly violate the GDPR, therefore they are illegal throughout the EU. Fines are VERY heavy, so this must not be taken lightly. The fines range up to 20 million Euro or 4 percent of a year's turnover (sic! Not profit!), whichever is HIGHER. Yes, Analytics is optional, and it's the decision of an admin, correct. But IMHO Tiki should inform the admin when he/she activates this, that compliance with current law must be observed, and that Analytics can be (very) problematic in this regard. And to be on the very safe side, IMHO there should be a checkbox that spells out as confirmation "Yes, I am aware of the compliance issues imposed by this". |
tracker item |
|
Please Note: Dogfood notice Enough already please
Noob here enjoying the site, enjoying the software and finding my way around. Thank you. It means spending a *lot* of time at the Tiki sites. I get the message already about the dogfood. Cool. But every day, every page load, I must dismiss this notice to uncover what is underneath. Or scroll the viewport out from under it. It is located on top of the navigation. Can we not have it fixed in the page above the navigation, or permanently dismissable once logged in, or ...? Can we just use the site now, and stop swatting at the javascript? :) I'm just setting up svn etc now. And wouldn't have the balls to make such a visible change right off the hop anyway. It's not real important obviously. But if somebody is there and knows and can do, it would make surfing the sites more pleasant... Cheers!! |
tracker item |
|
Please rename the start button in the wizards
{syntax type="tiki" editor="plain"} Please rename the start button of the wizards. The reason is that the translation function tra() is completely ignorant of context. And at least in German the problem arises that the imperative of starting, that "start" means, is different from the noun that marks the beginning of a calendar event. In English both are "start", but not in German. In German that is "Beginn" (as with all nouns with upper case 'b'), while the imperative of starting would be "beginne" (as with all verbs with lower case 'b'), or in the preferred more professional looking passive construction "beginnen". The verb "starten" also exists, with that it would either be "starten" or "starte", but this arises the problem that if I rename one, I must as a consequence also rename the other. It is not possible to correctly translate both! Because tra() is igorant of context... So I have to make a decision which wrong translation does lesser damage... So please find a different string for "Start". Preferrably, since it might take aeons before tra() becomes context sensitive, one that carries the context inside the string itself, like "start wizard". This should be a recommendation FOR ALL STRINGS throughout Tiki... |
tracker item |
|
Plugin Add to Cart to use existing data from tracker item
Plugin Add to Cart is used in conjunction with a tracker item (the product). In the tracker item we already have price and description however the Plugin Add to Cart need those field to be set manually. Extra maintenance and... dull :) The Plugin Add to Cart should be able to use the product information. |
tracker item |
|
Plugin List and ListExecute displays code when field is a tracker item title (link)
Once a tracker field is set as title, it turns to be a link to the tracker item. In certain (but several) condition when using a plugin List, ListExecute or the plugin Map this field(link) will be inserted into another link and then the display will be broken and it will show code instead of item link. (a link within a link is bad) Check the instance. First problem: There is nothing that can tells you from where come the issue and only after several experience and Jonny’s help we found out what it was. Anyone else (and new comers) won't have any idea why the display is broken. Second problem: __It is a pain !__ Workaround are messy; you have to duplicate fields (Name and Title), title has to be set to a different field (like Id) and start confusion or worst, previous setting that were ok turn to be broken. Would it be possible to have some kind of strip there ? (if the value is already a link, strip <a ...). There is a smarty function for that "Strip" couldn't it be easily set ? |
tracker item |
|
Plugin ListExecute with email sending garbage if tracker field type is file
It is not possible to use the plugin ListExecute to send an email that contain a tracker field type file. If you do so it will send different kind of un-useable code. There is a debate about inserting a file in an email and maybe this will be fixed/changed one day. In the meantime it will be cleaner to display proper error or warning something like "it is not possible..." |
tracker item |
|
plugin poll not working (on doc.tw.o at least)
Plugin poll is not working on doc.tw.o. No way to vote on the box... See it at: [http://doc.tikiwiki.org/PluginPoll] --- Update: weird behavior: I visited today the doc page about it, and it showed ok. I edited the page to say that there was not bug there any more, and after saving changes, the output is wrong again! So ???? I don't know what's happening... Please somebody else, have a llok (not urgent, but something is wrong here...) |
tracker item |
|
Plugin TrackerStat: allow showing the description of tracker fields in the display of results.
Plugin TrackerStat has no easy replacement with Plugin List, as far as a I know. When trackers are used to fill in questionaires, there are sometimes long phrases that are written in full in the description of the field, and the field name is just some short name to refer to it. When the user fills in the form, the field descriptions can be shown below the field. But when results are shown through PluginTrackerStat, no field description is shown, and in some cases, it's hard to understand the answers without the full text shown in the description of the field. This could be solved with a param to optionally display the field descriptions in the Plugin TrackerStat. - See it reproduced here: See it reproduced here: http://xavi-9794-5637.show.tikiwiki.org/tiki-index.php#contentvotingsystem-2 u: admin p: 12345 field: 12 How many days? {CODE()} 1 1 %33.33 <-> 1 10 %33.33 <-> 1 2 %33.33 <-> {CODE} How many days is almost meaningless here at result-display time. The description of the field needs to be shown also: "__How many days did you attend last year to the weeksly meetings of hte organization?__" |
tracker item |
|
Plugin TrackerStat: natural case sorting on the answers (text strings)
Plugin TrackerStat has no easy replacement with Plugin List, as far as a I know. We need to have the answers to a question (tracker field) sorted with natural case sorting. For instance, if you ask in the question a radio button showing options from 1 to 24, you will get the answers sorted as something like (copied from a production site): {CODE(ln="1")} 1 10 %3.12 <-> 1 11 %3.12 <-> 2 12 %6.25 <-> 1 13 %3.12 <-> 1 15 %3.12 <-> 5 16 %15.62 <-> 4 18 %12.50 <-> 1 2 %3.12 <-> 3 20 %9.38 <-> 1 21 %3.12 <-> 1 22 %3.12 <-> 1 24 %3.12 <-> 1 24 (Always) %3.12 <-> 3 3 %9.38 <-> 3 5 %9.38 <-> 2 6 %6.25 <-> 1 8 %3.12 <-> {CODE} See it reproduced here: http://xavi-9794-5637.show.tikiwiki.org/tiki-index.php#contentvotingsystem-2 u: admin p: 12345 field: 12 How many days? {CODE()} 1 1 %33.33 <-> 1 10 %33.33 <-> 1 2 %33.33 <-> {CODE} Answer related to "10" should be after the one related to answer number "2" PHP function natcasesort needs tobe used to sort answers. http://php.net/manual/en/function.natcasesort.php |
tracker item |
|
PluginAnnotation missplaces boxes in Tiki14
PluginAnnotation missplaces boxes in Tiki14 compared to Tiki12. Issue reproduced here: https://doc.tiki.org/PluginAnnotation+example Log in as Registered, and try to add a box somewhere in the image, you will see the red box drown somewhere else (missplaced to the right of your cursor). See it working as expected in Tiki12 (reproduced in a show instance here): http://xavi-9794-5777.show.tikiwiki.org/tiki-index.php?page=HomePage u: admin p: 12345 |
tracker item |
|
PluginCountdown: options on types :days, days + hours, hours only, etc
((doc:PluginCountdown)) a great idea. But showing time to the seconds is not a good default. Wish: Make options; Days, Days & hours, etc Should be an option as to how to handle once time is passed. __x days since__ or __the event has happened__ And locate time has no effect here: http://tikiwiki.org/TikiFestNY |
tracker item |
|
PluginIframe Approval on Tiki.org
The iframe plugin page on tiki.org needs its own plugin approved: http://doc.tiki.org/tiki-index.php?page=PluginIframe#Example |
tracker item |
|
PluginInclude not working properly in Tiki 6.2 and 6.1
Wiki plugin, when using with start and stop parameters does not include any text. It only includes the text when used without these parameters. Using Tiki 6.1 fresh code install, on past 6.0 db updated to 6.1. In using tiki 6.2 the problem persists. |
tracker item |
|
Plugins broken in Blog inn 1.9.2
When putting a plugin onto a blog post which requires parameters, the parameters are not passed in or are passed in as an &. This happens when the => syntax is used, or quotes are used around the parameter. These are otherwise fine when in a wiki page. Most plugins appear to be affected on my installation - which was an upgrade from 1.8.4 to 1.9.2. They render okay when viewing individual posts, or previewing, which leads me to beleive it is in tiki-blog_view.php somewhere. After diffing the files, the largest visible change was the addition of categories into the blog, this is however not affected by turning off the feature in admin. I am putting this high on my own priority list as I cannot upgrade my live site to 1.9.2 (although it has had some secuirty fixes put on it) until this is solved as I do not want to break my history of blog posts using plugins. Perhaps it is worth a shot on this site or tikiwiki.org to see if plugins are affected here as well with that. |
tracker item |
|
PluginVersions : doesn't work properly with more than 2 versions
Reopening -- regression in 3.x. See http://doc.tikiwiki.org/PluginVersion for an example --- Version 3 shows version 3, 2 and 1. See http://doc.tikiwiki.org/PluginVersions and try the test which has more than 2 versions Related: http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=800 |
tracker item |
|
Possible bug at creating base Tiki DB tables
The basic Tiki DB initalization IMHO contains an error. Maybe this is due to a change introduced later that made the INSERT incompatible to the CREATE. /db/tiki.sql contains this at lines 2867-2878: {CODE(Colors="Tiki")} DROP TABLE IF EXISTS `users_usergroups`; CREATE TABLE `users_usergroups` ( `userId` int(8) NOT NULL default '0', `groupName` varchar(255) NOT NULL default '', `created` int(14) default NULL, `expire` int(14) default NULL, PRIMARY KEY (`userId`,`groupName`(225)) ) ENGINE=MyISAM; INSERT INTO users_groups (`groupName`,`groupDesc`) VALUES ('Anonymous','Public users not logged'); INSERT INTO users_groups (`groupName`,`groupDesc`) VALUES ('Registered','Users logged into the system'); INSERT INTO users_groups (`groupName`,`groupDesc`) VALUES ('Admins','Administrator and accounts managers.'); {CODE} This should not work. Maybe the resulting error is just ignored? Values are entered into the non-existent column "groupDesc"... |
tracker item |
|
Possibly wrong help text for facets
(or, alternatively, wrong user input method) The admin UI for the facet feature describes, that the user shall enter a comma-separated list of categories, yet a multiselection window is presented. Interestingly, in /lib/prefs/category, where this help string comes from, is text input specified ?! If that would be presented, the text would be right, but somehow it is not... {CODE(Colors="Tiki")} 'category_custom_facets' => [ 'name' => tr('Generate custom facets from categories'), 'description' => tr('Comma-separated list of category IDs.'), 'type' => 'text', 'size' => 15, 'filter' => 'int', 'separator' => ',', 'default' => '', 'profile_reference' => 'category', ], {CODE} cf. screenshot (attachment) |
tracker item |
|
pretty tracker with tpl: get_pretty_fieldIds function fails
{syntax type="tiki" editor="plain"} tikiwiki-5.0.Beta1\lib\trackers\trackerlib.php, line 3584, in function get_pretty_fieldIds: $f = $smarty->get_filename($tpl); may be replaced by $resource_name = $smarty->get_filename($resource); $f = $smarty->_read_file($resource_name); |
tracker item |
|
Profile 'Dynamic items list' doesn't load in the admin panel & error shown through 'profile tester'
After an issue reported by a user in dev.t.o, and an example produced in the corresponding show.t.o site, I decided to create the corresponding profile to be able to test dynamic items list easily from now onwards in different tiki versions, etc. That's the rationale of this profile: https://profiles.tiki.org/Dynamic+items+list After I added the sections with data ("Objects in Products Tracker" and "Objects in Service Tracker"), the profile doesn't load any more in the Tiki admin panel for profiles. And when I added that yaml code in tiki-admin.php?page=profiles&cookietab=3 > "Profile Tester", then I got this error message: {CODE()} Fatal error: Call to a member function getRequiredProfiles() on a non-object in /var/www/trunk/lib/core/Tiki/Profile.php on line 479 {CODE} Any tips? --- And if I apply only the 2 sections defining the tracker and tracker fields (no sample data), then I get: {CODE()} An error occurred: Unknown objects are referenced: tiki://local/Test#products, tiki://local/Test#products_name, tiki://local/Test#products, tiki://local/Test#products_name, tiki://local/Test#products_version {CODE} --- After I removed the $ at the end of the objects defined elsewhere, then I ended up with this error through the Profile tester and only the section with trackers and tracker fields (no tracker data): {CODE()} Fatal error: Call to a member function getRequiredProfiles() on a non-object in /var/www/xavi-9794-4911/lib/core/Tiki/Profile.php on line 479 {CODE} |
tracker item |
|
profiles wiki handler: translations param doesn't work. To reproduce, see and apply profile: 'Consensus Forums'
Profiles wiki handler: translations param doesn't work. To reproduce, see and apply profile: http://profiles.tiki.org/Consensus+Forums This page: http://xavi-9794-5371.show.tikiwiki.org/tiki-index.php?page=Instructions+for+the+Consensus+Forums should be in the same trnaslation set as the equivalent Spanish one: http://xavi-9794-5371.show.tikiwiki.org/tiki-index.php?page=Instrucciones+de+los+Foros+de+Consenso This is how the pages are defined in the profile decalaration: {CODE()} objects: - type: wiki_page ref: consensus_forums_include data: name: Instructions for the Consensus Forums description: Instructions on how to use forums to help users seek consensus on discussion threads lang: en mode: create_or_update translations: consensus_forums_es_include content: wikicontent:Consensus_Forums_Instructions - type: wiki_page ref: consensus_forums_es_include data: name: Instrucciones de los Foros de Consenso description: Instrucciones sobre como users los foros para ayudar a los usuarios a buscar consensos en cada hilos de debate lang: es mode: create_or_update translations: consensus_forums_include content: wikicontent:Consensus_Forums_Instrucciones {CODE} However, the "translations" keyword doesn't seem to take effect. |
tracker item |
|
proposals/6x: Edit a Banning rule deletes the rule!
When you edit a banning rule, that rule gets deleted (at least, from the list at the Banning interface in Tiki). To reproduce: * go to tiki-admin_banning.php * add a rule for this ip "91.201.66.6" (real ip of spammers, btw) with the title "91.201.66.6_regular_spammers" * Check all features * Check the setting to activate the rule by dates * Select the maximum possible time frame (btyw, this only allows selecting within the same year: reported by somebody else already in another bug report; see [bug3643]) * add some custom message * save * click at the title of your rule in order to have it open for edition again for you * the rule is deleted from the list of rules, and the edit interface is empty --- confirmed in two different tiksi from different servers... (btw, 5.x is also affected) |
tracker item |
|
15.x: Improvements needed for mobile view of many *.t.o sites (dev, themes, doc, ...)
15.x: Improvements needed for mobile view of many *.t.o sites (dev, themes, doc, ...) {img src="display1077" thumb="box" width="800"} (1) No way to login at dev.t.o or doc.t.o, for instance, when browsing the page in the smartphone (tested with Chrome on Android, but it seems to be reproduced with a browser on a desktop and making it narrow enough as a smartphone) (2) There is no logo nor site name displayed in the top header of most *.t.o sites. OTher (non-tiki) bootstrap websites do display their logo and name when shown through smartphone. IS tehre anything that can be done in the Tiki side to fix this? (3) Fullscreen button is shown on top of the button at the top layer to display the logo and site name. Therefore, clicking there, fires the fullscreen in some cases. And when in full screen, in a smartphone, I couldn't come back to normal display mode clicking at that button in the smartphone for some reason, I had to fix the param in the url to get back to normal. (4) The submenu is not shown in dev.t.o and doc.t.o but it is shown in themes.t.o Why? How shall we edit the submenus so that they are shown in the smartphone display? Thanks |
tracker item |
|
15.x: Tracker: filter items is broken when value=label set (Radio, Dropdowns, ...) + plugin trackerfilter
12.x - 15.x: Tracker: filter items is broken when radio button with labels set (0=No,1=Yes,2=Dunno). No matches are found when there are some items which met the intended criteria. --It'll be-- reproduced in an attached intance --in short. Stay tuned!-- :-) {sign user="xavi" datetime="2016-02-09T12:21:27+00:00"} Login in here: http://xavi-9794-5810.show.tikiwiki.org/tiki-view_tracker.php?trackerId=1 u: admin p: 12345 You will see the field TestRaduio, with some values (0, 1 and 2; their labels, in fact) Try to filter by that field: http://xavi-9794-5810.show.tikiwiki.org/tiki-view_tracker.php?trackerId=1&status=o&sort_mode=f__asc&filterfield=8&filtervalue%5B1%5D=&filtervalue%5B2%5D=&filtervalue_other=&filtervalue%5B3%5D=5+%28high%29&filtervalue%5B8%5D=0%3DNo&filter=Filter# --- __Update:__ {sign user="xavi" datetime="2016-02-10T10:42:06+00:00"} the problem is also found (and still unsolved) at teh trackerfilter level. Sorry, I tried for one hour, but I couldn't get the right syntax to port this type of fix there also. :-/ To reproduce, see it here: http://xavi-9794-5810.show.tikiwiki.org/tiki-index.php?page=HomePage __The issue is reproduced also for dropdown fields when labels are set, etc. See it reproduced with field "Priority" (Dropdown). __ __Reproduced also with "Dropdown with other" (field __Location__) in the tracker itself, but it works as expceted through Plugin TrackerFilter.__ Does work: http://xavi-9794-5810.show.tikiwiki.org/tiki-index.php?page=HomePage Doesn't work: http://xavi-9794-5810.show.tikiwiki.org/tiki-view_tracker.php?trackerId=1&status=o&sort_mode=f__asc&filterfield=2&filtervalue%5B1%5D=&filtervalue%5B2%5D=0%3Droom+1.1+%2855+seats%29&filtervalue_other=&filtervalue%5B3%5D=5%3Dhighest&filtervalue%5B9%5D=y&filtervalue%5B10%5D%5B%5D=1&filter=Filter# Multiselect seems to work well, as expected, in both tracker itself and plugin trackerfilter. |
tracker item |
!! __Home Page - logged in__
Deprecated: Array and string offset access syntax with curly braces is deprecated in /tiki-sefurl.php on line 193
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/init/initlib.php on line 245
Deprecated: Array and string offset access syntax with curly braces is deprecated in /vendor_bundled/vendor/h5p/h5p-core/h5p.classes.php on line 2590
Deprecated: Array and string offset access syntax with curly braces is deprecated in /vendor_bundled/vendor/h5p/h5p-core/h5p-development.class.php on line 70
Deprecated: Unparenthesized `a ? b : c ? d : e` is deprecated. Use either `(a ? b : c) ? d : e` or `a ? b : (c ? d : e)` in /tiki-setup_base.php on line 223
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/core/Tiki/MemoryLimit.php on line 45
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/tikilib.php on line 416
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/tikilib.php on line 1925
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/tikilib.php on line 5147
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/tikilib.php on line 5147
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/tikilib.php on line 6448
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/modules/modlib.php on line 554
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/userslib.php on line 369
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/userslib.php on line 371
Deprecated: The behavior of unparenthesized expressions containing both '.' and '+'/'-' will change in PHP 8: '+'/'-' will take a higher precedence in /lib/userslib.php on line 8313
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/core/Perms/Accessor.php on line 118
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/core/Perms/Accessor.php on line 118
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/parser/parserlib.php on line 275
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/parser/parserlib.php on line 1442
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/core/WikiParser/PluginMatcher.php on line 389
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/core/WikiParser/PluginMatcher.php on line 602
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/core/WikiParser/PluginArgumentParser.php on line 27
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/core/WikiParser/PluginArgumentParser.php on line 35
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/core/WikiParser/PluginArgumentParser.php on line 39
!!__Editing Home Page__
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/wiki/editlib.php on line 1088
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/toolbars/toolbarslib.php on line 870
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/toolbars/toolbarslib.php on line 873
!! __Entering admin main page__
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/prefslib.php on line 142
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/core/Search/MySql/FieldQueryBuilder.php on line 31
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/core/Search/MySql/FieldQueryBuilder.php on line 41
!!__Search Page__
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/init/initlib.php on line 245
Deprecated: Array and string offset access syntax with curly braces is deprecated in /vendor_bundled/vendor/h5p/h5p-core/h5p.classes.php on line 2590
Deprecated: Array and string offset access syntax with curly braces is deprecated in /vendor_bundled/vendor/h5p/h5p-core/h5p-development.class.php on line 70
Deprecated: Unparenthesized `a ? b : c ? d : e` is deprecated. Use either `(a ? b : c) ? d : e` or `a ? b : (c ? d : e)` in /tiki-setup_base.php on line 223
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/core/Tiki/MemoryLimit.php on line 45
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/tikilib.php on line 416
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/tikilib.php on line 1925
Deprecated: Array and string offset access syntax with curly braces is deprecated in/lib/tikilib.php on line 5147
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/tikilib.php on line 5147
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/tikilib.php on line 6448
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/modules/modlib.php on line 554
Deprecated: Array and string offset access syntax with curly braces is deprecated in/lib/userslib.php on line 369
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/userslib.php on line 371
Deprecated: The behavior of unparenthesized expressions containing both '.' and '+'/'-' will change in PHP 8: '+'/'-' will take a higher precedence in /lib/userslib.php on line 8313
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/core/Perms/Accessor.php on line 118
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/core/Perms/Accessor.php on line 118
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/parser/parserlib.php on line 275
Deprecated: Array and string offset access syntax with curly braces is deprecated in /lib/parser/parserlib.php on line 1442
!!__File Gallery__
Deprecated: Unparenthesized `a ? b : c ? d : e` is deprecated. Use either `(a ? b : c) ? d : e` or `a ? b : (c ? d : e)` in /fgal_listing_conf.php on line 122
I have 6 other sites running and I can not change the PHP version to anything less.