You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I'm in an empty sys folder and try to create a new record, I directly end up with this error message:
(1/1) #1476107295 TYPO3\CMS\Core\Error\Exception
PHP Warning: Trying to access array offset on value of type null in yoast_seo/Classes/Form/Element/SnippetPreview.php line 202
I debugged the SnippetPreview a little bit and it seem that the wrong record is queried:
In my case, the both parameters where the table name specified above and as $recordId the uid of my sys_folder was used.
Long story short: I think the main problem is, that EXT:yoast_seo tries to generate a preview URL for not yet existing record which doesn't make sense at all.
How can we reproduce this behavior?
use RecordUtility::configureForRecord() for a custom table
create an empty sys_folder
create a new record of the above mentioned type
Technical info
TYPO3 version: 11.5
Yoast SEO version: 9.0.3
The text was updated successfully, but these errors were encountered:
peterkraume
added a commit
to peterkraume/Yoast-SEO-for-TYPO3
that referenced
this issue
Apr 26, 2024
Please give us a description of what happened.
I'm using the
RecordUtility
to add Yoast SEO fields to a custom table:When I'm in an empty sys folder and try to create a new record, I directly end up with this error message:
I debugged the
SnippetPreview
a little bit and it seem that the wrong record is queried:Yoast-SEO-for-TYPO3/Classes/Form/Element/SnippetPreview.php
Line 171 in c1e4ae9
In my case, the both parameters where the table name specified above and as
$recordId
the uid of my sys_folder was used.Long story short: I think the main problem is, that EXT:yoast_seo tries to generate a preview URL for not yet existing record which doesn't make sense at all.
How can we reproduce this behavior?
RecordUtility::configureForRecord()
for a custom tableTechnical info
The text was updated successfully, but these errors were encountered: