<?xml version="1.0" encoding="utf-8"?>
<!--RSS generated by Flaimo.com RSS Builder [2026-07-31 08:59:58]-->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"><channel><docs>https://bugs.limesurvey.org/</docs><link>https://bugs.limesurvey.org/</link><description><![CDATA[LimeSurvey bugs and feature requests - Issues]]></description><title>LimeSurvey bugs and feature requests - Issues</title><image><title>LimeSurvey bugs and feature requests - Issues</title><url>https://bugs.limesurvey.org/images/mantis_logo.png</url><link>https://bugs.limesurvey.org/</link><description><![CDATA[LimeSurvey bugs and feature requests - Issues]]></description></image><language>en</language><category>All Projects</category><ttl>10</ttl><dc:language>en</dc:language><sy:updatePeriod>hourly</sy:updatePeriod><sy:updateFrequency>1</sy:updateFrequency><item><title>20624: DB crash when updating from 7.0.5 to 7.0.7 due to missing DB version check</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20624</link><description><![CDATA[While upgrading **LimeSurvey 7.0.5** to **7.0.7**, we encountered a database update failure on a server running **MariaDB 10.1.48**.&lt;br /&gt;
&lt;br /&gt;
As a temporary workaround, we were able to complete the update by changing the column type from `JSON` to `LONGTEXT` in:&lt;br /&gt;
`application/helpers/update/updates/Update_709.php` (line **19**)&lt;br /&gt;
&lt;br /&gt;
```php&lt;br /&gt;
addColumn(&quot;{{responses_&quot; . $sid . &quot;}}&quot;, &quot;Q{$parent_qid}&quot;, &quot;LONGTEXT&quot;);&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
However, we believe the actual issue is that the updater starts the database migration without first verifying that the database server meets the documented minimum requirements.]]></description><category>ComfortUpdate</category><pubDate>Thu, 30 Jul 2026 19:24:26 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20624</guid><comments>https://bugs.limesurvey.org/view.php?id=20624#bugnotes</comments></item><item><title>20623: HTTP Authorization header field not treated as case-insensitive leading to new editor not working</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20623</link><description><![CDATA[HTTP Authorization header field not treated as case-insensitive leading to new editor not working&lt;br /&gt;
&lt;br /&gt;
In 'application/libraries/Api/Rest/Endpoint/EndpointFactory.php'[1], the check for the &quot;Authorization&quot; header field is not case-insensitive, as mandated by the HTTP standard.&lt;br /&gt;
Thus, the new editor won't work (i.e. be stuck with &quot;Checking permissions…&quot;) when ran behind a http server or proxy that uses lower cases header fields (for example haproxy in HTTP/2 mode, as HTTP/2 requires the conversion of header fields to lower case). &lt;br /&gt;
&lt;br /&gt;
[1] &lt;a href=&quot;https://github.com/LimeSurvey/LimeSurvey/blob/9e6aa71beb752f11b68f03c33e554c81c71cdddc/application/libraries/Api/Rest/Endpoint/EndpointFactory.php#L232-L238&quot; rel=&quot;noopener,nofollow&quot;&gt;https://github.com/LimeSurvey/LimeSurvey/blob/9e6aa71beb752f11b68f03c33e554c81c71cdddc/application/libraries/Api/Rest/Endpoint/EndpointFactory.php#L232-L238&lt;/a&gt;]]></description><category>Survey editing</category><pubDate>Thu, 30 Jul 2026 17:46:52 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20623</guid><comments>https://bugs.limesurvey.org/view.php?id=20623#bugnotes</comments></item><item><title>20622: Mandatory ranking questions can not be answered</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20622</link><description><![CDATA[There is a possible issue specifically related to mandatory validation for Ranking questions. You can not get to the next page even if all items have been ranked.&lt;br /&gt;
The issue can be reproduced on a completely new survey with a newly created Ranking question and no custom validation equations configured.]]></description><category>Survey taking</category><pubDate>Thu, 30 Jul 2026 12:40:34 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20622</guid><comments>https://bugs.limesurvey.org/view.php?id=20622#bugnotes</comments></item><item><title>20620: statistic export failed with output format PDF and Excel</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20620</link><description><![CDATA[hello,&lt;br /&gt;
&lt;br /&gt;
when exporting a statistic from a survey with the output format &quot;PDF&quot; and &quot;Excel&quot;, the statistic export failed.]]></description><category>Statistics</category><pubDate>Wed, 29 Jul 2026 16:38:39 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20620</guid><comments>https://bugs.limesurvey.org/view.php?id=20620#bugnotes</comments></item><item><title>20619: Security update available - although LimeSurvey is updated to the latest 6.x version</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20619</link><description><![CDATA[We currently have two recent versions, one in the 6.x line and one in the 7.x line. Both are considered stable.&lt;br /&gt;
Since we cannot switch to the 7.x version anytime soon, but security updates are available for the 6.x version, the message “Security update available” should only be displayed if not all security patches for the 6.x version have been installed. &lt;br /&gt;
&lt;br /&gt;
This leads to uncertainty and unease among users, as this gives the impression that LimeSurvey is being operated with security vulnerabilities, while at the same time handling sensitive data (surveys).]]></description><category>Usability/user experience</category><pubDate>Fri, 24 Jul 2026 15:09:39 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20619</guid><comments>https://bugs.limesurvey.org/view.php?id=20619#bugnotes</comments></item><item><title>20616: Invalid datetime format: 1292 Incorrect datetime value</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20616</link><description><![CDATA[CDbCommand ha riportato un errore nell'esecuzione della query SQL: SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '0000-00-00 00:00:00' for column 'lastmodified' at row 23. The SQL statement executed was: ALTER TABLE `lime_surveys` ADD `showregisterpolicy` varchar(1) NOT NULL DEFAULT 'I']]></description><category>Installation</category><pubDate>Thu, 23 Jul 2026 16:30:59 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20616</guid><comments>https://bugs.limesurvey.org/view.php?id=20616#bugnotes</comments></item><item><title>20613: Survey logic overview option shows error 500</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20613</link><description><![CDATA[Have a survey developed in Limesurvey version 6, after importing it, and then click in the &quot;Survey logic overview&quot; option, an error appears in screen: &quot;500: Internal Server Error - array_merge(): Argument #2 must be of type array, null given&quot;&lt;br /&gt;
Issue confirmed in a locally installed Limesurvey 7.0.5 and in the demo site (demo.limesurvey.org) with Limesurvey 7.0.4&lt;br /&gt;
Tested it in the latest version of Limesurvey 6 available (6.7.11), and no issues.]]></description><category>Survey editing</category><pubDate>Tue, 28 Jul 2026 21:43:52 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20613</guid><comments>https://bugs.limesurvey.org/view.php?id=20613#bugnotes</comments></item><item><title>20612: Limesurvey crashing when adding a participant to a imported survey with attributes</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20612</link><description><![CDATA[When importing a survey previously developed with additional participant attributes, when adding the first participant, Limesurvey doesn't request the values of aditional attributes, and when saving the participant, Limesurvey crashes with an 500 error. Doesn't happen after trying to add the first participant.]]></description><category>Survey participants (Tokens)</category><pubDate>Thu, 23 Jul 2026 16:10:22 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20612</guid><comments>https://bugs.limesurvey.org/view.php?id=20612#bugnotes</comments></item><item><title>20611: New feature to exclude items at quick translation</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20611</link><description><![CDATA[The quick translation feature is a very useful tool, especially when making use of a Google Translate API key to automatically translate items to different languages. There are some drawbacks though: When using the auto-translation, it always adjusts all items on the current page/tab. But if parts of the translation have already been reviewed by a native speaker, or if there are equation questions, which the auto-translate sometimes messes up, then you need to redo the whole translation process after the auto-translation was done. &lt;br /&gt;
&lt;br /&gt;
This can easily be solved by having a checkbox for every item, which is enabled by default, but offers the ability for the user to disable the translation feature for certain items. &lt;br /&gt;
&lt;br /&gt;
We could try to develop this and provide a pull request. Is this considered a helpful feature? Then we would give it a try.]]></description><category>Translation</category><pubDate>Fri, 17 Jul 2026 16:58:35 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20611</guid><comments>https://bugs.limesurvey.org/view.php?id=20611#bugnotes</comments></item><item><title>20609: Admin notification url are not updated as link</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20609</link><description><![CDATA[Admin notification URLs like VIEWRESPONSEURL are not set as link]]></description><category>Other</category><pubDate>Wed, 29 Jul 2026 17:40:48 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20609</guid><comments>https://bugs.limesurvey.org/view.php?id=20609#bugnotes</comments></item><item><title>20608: datasecurity_notice_label is not rendered correctly with "Collapsible text" and "All in one" survey format</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20608</link><description><![CDATA[This is a follow up for &lt;a href=&quot;https://bugs.limesurvey.org/view.php?id=19852&quot;&gt;19852&lt;/a&gt;.]]></description><category>Survey editing</category><pubDate>Fri, 17 Jul 2026 14:04:12 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20608</guid><comments>https://bugs.limesurvey.org/view.php?id=20608#bugnotes</comments></item><item><title>20607: Placeholder fields are empty in the Email Templates editor</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20607</link><description><![CDATA[When editing an Email Template, the list of available placeholder fields is empty.&lt;br /&gt;
&lt;br /&gt;
The issue does not affect all email template types.&lt;br /&gt;
&lt;br /&gt;
In the Email Templates editor:&lt;br /&gt;
For Invitation and Reminder, the list of available replacement fields is displayed correctly.&lt;br /&gt;
For Confirmation, Registration, Basic admin notification, and Detailed admin notification, the replacement field panel displays the message:&lt;br /&gt;
&lt;br /&gt;
&gt; No replacement variable available for this field]]></description><category>Other</category><pubDate>Tue, 21 Jul 2026 18:04:23 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20607</guid><comments>https://bugs.limesurvey.org/view.php?id=20607#bugnotes</comments></item><item><title>20605: Non consistent branch label</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20605</link><description><![CDATA[In the Comfort Update screen, the message says there is an unsable update but actually it is a stable one.&lt;br /&gt;
See screenshot]]></description><category>ComfortUpdate</category><pubDate>Tue, 21 Jul 2026 18:05:02 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20605</guid><comments>https://bugs.limesurvey.org/view.php?id=20605#bugnotes</comments></item><item><title>20600: When try to create dummy participant : page must be reloaded</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20600</link><description><![CDATA[When try to create dummy participant, if you don't reload the page, no action is done when you clickthe 1st time &lt;br /&gt;
This happen with mandatory attribute.]]></description><category>Usability/user experience</category><pubDate>Tue, 07 Jul 2026 19:44:35 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20600</guid><comments>https://bugs.limesurvey.org/view.php?id=20600#bugnotes</comments></item><item><title>20599: When questions have a relevance equation, mandatory questions are not enforced.</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20599</link><description><![CDATA[I am seeing issues in a survey, where I have mandatory questions, and I am able to move forward without answering them&lt;br /&gt;
The issue seems to happen when questions have a relevance equation... that seems to kill the enforcement of mandatory questions.&lt;br /&gt;
When the questions don't have relevance equations, the mandatory rule is enforced.&lt;br /&gt;
&lt;br /&gt;
This happens on v6 and v7]]></description><category>Survey taking</category><pubDate>Thu, 09 Jul 2026 08:57:18 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20599</guid><comments>https://bugs.limesurvey.org/view.php?id=20599#bugnotes</comments></item><item><title>20598: Token overwrite when opening multiple survey tokens in different tabs of the same browser</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20598</link><description><![CDATA[When a user opens two distinct token links for the same survey in two different tabs of the same browser session, LimeSurvey overwrites the active token session data with the most recently loaded one. If the user goes back to the first tab and tries to save or proceed, the response data gets cross-contaminated or associated with the second token.]]></description><category>Survey participants (Tokens)</category><pubDate>Thu, 09 Jul 2026 12:35:34 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20598</guid><comments>https://bugs.limesurvey.org/view.php?id=20598#bugnotes</comments></item><item><title>20596: Panel-Integration parameter (Survey-URL-Parameter) missing after copy</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20596</link><description><![CDATA[When I copy a survey, the panel integration parameters are missing in the result.&lt;br /&gt;
&lt;br /&gt;
When using export / import to &quot;copy&quot; a survey, the panel integration parameters are not missing.]]></description><category>Survey editing</category><pubDate>Tue, 21 Jul 2026 18:10:46 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20596</guid><comments>https://bugs.limesurvey.org/view.php?id=20596#bugnotes</comments></item><item><title>20595: Printable Survey not showing "other", after importing via txt</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20595</link><description><![CDATA[After importing a Survey via txt the &quot;export&quot; -&gt; &quot;Printable Survey&quot; view does not show any other fields.&lt;br /&gt;
A workaround for this is: After importing open every question containing an other field, then saving the question (without any changes).&lt;br /&gt;
It seems as if saving the questions changes some parameter in the background, which is necessary for the Printable survey view.&lt;br /&gt;
&lt;br /&gt;
Also it seems that the issue:&lt;br /&gt;
   only occurs on txt import&lt;br /&gt;
   applies to all question that have a built in other field option&lt;br /&gt;
   is unaffected by other position and custom text]]></description><category>Import/Export</category><pubDate>Mon, 06 Jul 2026 12:03:24 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20595</guid><comments>https://bugs.limesurvey.org/view.php?id=20595#bugnotes</comments></item><item><title>20594: It is not possible to delete answer options/subquestions after upgrading to 7.0.4+260620</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20594</link><description><![CDATA[After upgrading to LimeSurvey 7.0.4+260620 via Comfort Update, answer options can be created but cannot be deleted. The issue appears to affect all question types with answer options and subquestions.]]></description><category>Question editor</category><pubDate>Fri, 24 Jul 2026 14:37:47 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20594</guid><comments>https://bugs.limesurvey.org/view.php?id=20594#bugnotes</comments></item><item><title>20589: Direct link to view single response no longer opens a dedicated page since v7 — only a modal/popup, breaking shareable links</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20589</link><description><![CDATA[## Expected Behavior&lt;br /&gt;
&lt;br /&gt;
In previous LimeSurvey versions (pre-v7), clicking view/edit on a response opened a dedicated page with its own unique URL, e.g.:&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;https://umfrage.example.tld/responses/view?surveyId=532561&amp;id=280&quot; rel=&quot;noopener,nofollow&quot;&gt;https://umfrage.example.tld/responses/view?surveyId=532561&amp;id=280&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
This URL was directly shareable, colleagues or reviewers could be sent a link straight to a specific response without needing to log in, navigate to the survey, and manually search for the response ID.&lt;br /&gt;
&lt;br /&gt;
## Problem&lt;br /&gt;
&lt;br /&gt;
* Old-style direct links (responses/view?surveyId=X&amp;id=Y) still resolve to a working page (confirmed on our instance), but this is no longer reachable from the UI itself.&lt;br /&gt;
* The response list now only supports a popup for viewing/editing individual responses, and popups cannot be bookmarked, linked, or shared via URL.&lt;br /&gt;
* This breaks existing workflows for teams that share direct links to specific responses (e.g. for QA, moderation, or cross-referencing with partners).&lt;br /&gt;
&lt;br /&gt;
## Suggested Fix&lt;br /&gt;
&lt;br /&gt;
Restore the option to open a response in its own dedicated page (either as default behavior or as a user-selectable alternative to the popup), so the URL updates to reflect the currently viewed response and can be copied/shared.&lt;br /&gt;
&lt;br /&gt;
Alternatively: make the popup update the browser URL (e.g. via history.pushState) so the current response state is reflected in a shareable link, similar to how many modern SPA implementations preserve deep-linkability even inside modals.]]></description><category>Response browsing</category><pubDate>Wed, 01 Jul 2026 15:24:01 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20589</guid><comments>https://bugs.limesurvey.org/view.php?id=20589#bugnotes</comments></item><item><title>20588: Error while import participants for csv file</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20588</link><description><![CDATA[Error while import participants for csv file&lt;br /&gt;
&lt;br /&gt;
Invalid access codes skipped when the token field is filled in&lt;br /&gt;
&lt;br /&gt;
for example:&lt;br /&gt;
&lt;br /&gt;
tid,firstname,lastname,email,emailstatus,token,language,validfrom,validuntil,invited,reminded,remindercount,completed,usesleft&lt;br /&gt;
&quot;1&quot;,&quot;first&quot;,&quot;last&quot;,&quot;&lt;a href=&quot;mailto:first.last@gmail.com&quot;&gt;first.last@gmail.com&lt;/a&gt;&quot;,&quot;OK&quot;,&quot;DIOnqyPDjZJPDws&quot;,&quot;pl&quot;,&quot;&quot;,&quot;&quot;,&quot;N&quot;,&quot;N&quot;,&quot;0&quot;,&quot;N&quot;,&quot;1&quot;&lt;br /&gt;
&lt;br /&gt;
When the token field is empty import executes successfully.]]></description><category>Survey participants (Tokens)</category><pubDate>Wed, 22 Jul 2026 12:04:03 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20588</guid><comments>https://bugs.limesurvey.org/view.php?id=20588#bugnotes</comments></item><item><title>20586: Unabole to use installer GUI whith nginx or IIS</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20586</link><description><![CDATA[When trying to install a v7 version with a not configured nginx for url rewriting, redirection is /index.php/installer goes to a 404]]></description><category>Installation</category><pubDate>Tue, 30 Jun 2026 17:01:06 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20586</guid><comments>https://bugs.limesurvey.org/view.php?id=20586#bugnotes</comments></item><item><title>20585: New editor throws error - 404 could not resolve request editor</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20585</link><description><![CDATA[In a fresh install of limesurvey 7.0.5 I can create and edit a survey with the classic editor. As soon as I switch to the new editor I can neither edit an existing survey nor create a new one.&lt;br /&gt;
&lt;br /&gt;
 To be more specific, when i try to create a new survey a survey is created but the redirect to the edit view of this new survey instantly throws an error.]]></description><category>Question editor</category><pubDate>Wed, 15 Jul 2026 12:10:58 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20585</guid><comments>https://bugs.limesurvey.org/view.php?id=20585#bugnotes</comments></item><item><title>20582: Several deprecation errors when using version 7.0.5 with PHP 8.4</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20582</link><description><![CDATA[I had to modify several files in order to get rid of a deprecation message:&lt;br /&gt;
&lt;br /&gt;
 PHP Deprecated:  DI\autowire(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /var/www/vhosts/wordpress/htdocs/umfrage.dgb-bildungswerk.de/vendor/php-di/php-di/src/functions.php on line 48&lt;br /&gt;
 PHP Deprecated:  DI\create(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /var/www/vhosts/wordpress/htdocs/umfrage.dgb-bildungswerk.de/vendor/php-di/php-di/src/functions.php on line 35&lt;br /&gt;
 PHP Deprecated:  GoldSpecDigital\ObjectOrientedOAS\Objects\Schema::boolean(): Implicitly marking parameter $objectId as nullable is deprecated, the explicit nullable type must be used instead in /var/www/vhosts/wordpress/htdocs/umfrage.dgb-bildungswerk.de/vendor/goldspecdigital/oooas/src/Objects/Schema.php on line 232&lt;br /&gt;
 PHP Deprecated:  GoldSpecDigital\ObjectOrientedOAS\Objects\Schema::integer(): Implicitly marking parameter $objectId as nullable is deprecated, the explicit nullable type must be used instead in /var/www/vhosts/wordpress/htdocs/umfrage.dgb-bildungswerk.de/vendor/goldspecdigital/oooas/src/Objects/Schema.php on line 241&lt;br /&gt;
 PHP Deprecated:  GoldSpecDigital\ObjectOrientedOAS\Objects\Schema::number(): Implicitly marking parameter $objectId as nullable is deprecated, the explicit nullable type must be used instead in /var/www/vhosts/wordpress/htdocs/umfrage.dgb-bildungswerk.de/vendor/goldspecdigital/oooas/src/Objects/Schema.php on line 250&lt;br /&gt;
 PHP Deprecated:  GoldSpecDigital\ObjectOrientedOAS\Objects\Schema::object(): Implicitly marking parameter $objectId as nullable is deprecated, the explicit nullable type must be used instead in /var/www/vhosts/wordpress/htdocs/umfrage.dgb-bildungswerk.de/vendor/goldspecdigital/oooas/src/Objects/Schema.php on line 259&lt;br /&gt;
 PHP Deprecated:  GoldSpecDigital\ObjectOrientedOAS\Objects\Schema::string(): Implicitly marking parameter $objectId as nullable is deprecated, the explicit nullable type must be used instead in /var/www/vhosts/wordpress/htdocs/umfrage.dgb-bildungswerk.de/vendor/goldspecdigital/oooas/src/Objects/Schema.php on line 268&lt;br /&gt;
&lt;br /&gt;
./vendor/php-di/php-di/src/Proxy/ProxyFactory.php&lt;br /&gt;
43c43&lt;br /&gt;
&lt;     public function __construct(bool $writeProxiesToFile = false, ?string $proxyDirectory = null)&lt;br /&gt;
---&lt;br /&gt;
&gt;     public function __construct(bool $writeProxiesToFile = false, string $proxyDirectory = null)&lt;br /&gt;
&lt;br /&gt;
./vendor/php-di/php-di/src/Definition/Helper/CreateDefinitionHelper.php&lt;br /&gt;
56c56&lt;br /&gt;
&lt;     public function __construct(?string $className = null)&lt;br /&gt;
---&lt;br /&gt;
&gt;     public function __construct(string $className = null)&lt;br /&gt;
&lt;br /&gt;
./vendor/php-di/php-di/src/Definition/Resolver/ParameterResolver.php&lt;br /&gt;
39,40c39,40&lt;br /&gt;
&lt;         ?MethodInjection $definition = null,&lt;br /&gt;
&lt;         ?ReflectionMethod $method = null,&lt;br /&gt;
---&lt;br /&gt;
&gt;         MethodInjection $definition = null,&lt;br /&gt;
&gt;         ReflectionMethod $method = null,&lt;br /&gt;
&lt;br /&gt;
./vendor/php-di/php-di/src/Definition/Resolver/ObjectCreator.php&lt;br /&gt;
212c212&lt;br /&gt;
&lt;     public static function setPrivatePropertyValue(?string $className, $object, string $propertyName, $propertyValue)&lt;br /&gt;
---&lt;br /&gt;
&gt;     public static function setPrivatePropertyValue(string $className = null, $object, string $propertyName, $propertyValue)&lt;br /&gt;
&lt;br /&gt;
./vendor/php-di/php-di/src/Definition/Source/DefinitionArray.php&lt;br /&gt;
39c39&lt;br /&gt;
&lt;     public function __construct(array $definitions = [], ?Autowiring $autowiring = null)&lt;br /&gt;
---&lt;br /&gt;
&gt;     public function __construct(array $definitions = [], Autowiring $autowiring = null)&lt;br /&gt;
&lt;br /&gt;
./vendor/php-di/php-di/src/Definition/Source/Autowiring.php&lt;br /&gt;
23c23&lt;br /&gt;
&lt;     public function autowire(string $name, ?ObjectDefinition $definition = null);&lt;br /&gt;
---&lt;br /&gt;
&gt;     public function autowire(string $name, ObjectDefinition $definition = null);&lt;br /&gt;
&lt;br /&gt;
./vendor/php-di/php-di/src/Definition/Source/DefinitionNormalizer.php&lt;br /&gt;
46c46&lt;br /&gt;
&lt;     public function normalizeRootDefinition($definition, string $name, ?array $wildcardsReplacements = null) : Definition&lt;br /&gt;
---&lt;br /&gt;
&gt;     public function normalizeRootDefinition($definition, string $name, array $wildcardsReplacements = null) : Definition&lt;br /&gt;
&lt;br /&gt;
./vendor/php-di/php-di/src/Definition/Source/AnnotationBasedAutowiring.php&lt;br /&gt;
56c56&lt;br /&gt;
&lt;     public function autowire(string $name, ?ObjectDefinition $definition = null)&lt;br /&gt;
---&lt;br /&gt;
&gt;     public function autowire(string $name, ObjectDefinition $definition = null)&lt;br /&gt;
&lt;br /&gt;
./vendor/php-di/php-di/src/Definition/ObjectDefinition.php&lt;br /&gt;
72c72&lt;br /&gt;
&lt;     public function __construct(string $name, ?string $className = null)&lt;br /&gt;
---&lt;br /&gt;
&gt;     public function __construct(string $name, string $className = null)&lt;br /&gt;
88c88&lt;br /&gt;
&lt;     public function setClassName(?string $className = null)&lt;br /&gt;
---&lt;br /&gt;
&gt;     public function setClassName(string $className = null)&lt;br /&gt;
186c186&lt;br /&gt;
&lt;     public function setLazy(?bool $lazy = null)&lt;br /&gt;
---&lt;br /&gt;
&gt;     public function setLazy(bool $lazy = null)&lt;br /&gt;
&lt;br /&gt;
./vendor/php-di/php-di/src/Container.php&lt;br /&gt;
98,100c98,100&lt;br /&gt;
&lt;         ?MutableDefinitionSource $definitionSource = null,&lt;br /&gt;
&lt;         ?ProxyFactory $proxyFactory = null,&lt;br /&gt;
&lt;         ?ContainerInterface $wrapperContainer = null&lt;br /&gt;
---&lt;br /&gt;
&gt;         MutableDefinitionSource $definitionSource = null,&lt;br /&gt;
&gt;         ProxyFactory $proxyFactory = null,&lt;br /&gt;
&gt;         ContainerInterface $wrapperContainer = null&lt;br /&gt;
&lt;br /&gt;
./vendor/php-di/php-di/src/ContainerBuilder.php&lt;br /&gt;
283c283&lt;br /&gt;
&lt;     public function writeProxiesToFile(bool $writeToFile, ?string $proxyDirectory = null) : self&lt;br /&gt;
---&lt;br /&gt;
&gt;     public function writeProxiesToFile(bool $writeToFile, string $proxyDirectory = null) : self]]></description><category>Survey editing</category><pubDate>Mon, 29 Jun 2026 16:27:08 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20582</guid><comments>https://bugs.limesurvey.org/view.php?id=20582#bugnotes</comments></item><item><title>20581: application/controllers/ResponsesController.php crashes (due to php 8.4)</title><author></author><link>https://bugs.limesurvey.org/view.php?id=20581</link><description><![CDATA[The display of responses generates a php error: &lt;br /&gt;
ResponsesController::actionDeleteAttachments(): Implicitly marking parameter $responseId as nullable is deprecated, the explicit nullable type must be used instead&lt;br /&gt;
/srv/www/formulaire.unige.ch/html_root/outils/limeemploi/application/controllers/ResponsesController.php(808)&lt;br /&gt;
&lt;br /&gt;
I've patched it adding a &quot;?&quot; before the second &quot;int&quot; on line 808:&lt;br /&gt;
&lt;br /&gt;
diff ResponsesController.php.00 ResponsesController.php&lt;br /&gt;
808c808&lt;br /&gt;
&lt;br /&gt;
&lt;     public function actionDeleteAttachments(int $surveyId, int $responseId = null): void&lt;br /&gt;
---&lt;br /&gt;
&gt;     public function actionDeleteAttachments(int $surveyId, ?int $responseId = null): void&lt;br /&gt;
&lt;br /&gt;
I've checked, the error is still in v  6.17.10]]></description><category>Response browsing</category><pubDate>Mon, 29 Jun 2026 16:48:43 +0200</pubDate><guid>https://bugs.limesurvey.org/view.php?id=20581</guid><comments>https://bugs.limesurvey.org/view.php?id=20581#bugnotes</comments></item></channel></rss>
