![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 6 weeks ago
Closed 6 weeks ago
#65357 closed defect (bug) (worksforme)
Widget pages broken
| Reported by: | fleig | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Awaiting Review |
| Component: | Widgets | Version: | 7.0 |
| Severity: | major | Keywords: | reporter-feedback |
| Cc: | Focuses: | ui |
Description
After updating to 7.0, the widget admin page is broken: the classic mode has no right column where widgets are added and the block mode just shows unstyled HTML of the top widget's form function. Because of this, he widgets cannot be edited, added or deleted.
The whole customize page is also borken in the same unstyled HTML described above.
In the front end, everything appears to be working normally.
Change History (2)
#2
@
6 weeks ago
- Resolution → worksforme
- Status new → closed
Hi!
I figured it out: a bit of new code in one of the widgets was thowing a critical site error, but only on the customize page. On the classic widgets page, it only prevented the loading of the right hand column.]
If it helps, this is the code that was causing problems:
<p>
<input class="checkbox"
<?php if ( isset( $instance['use_pinned'] ) && $instance['use_pinned']=='true' ) { echo 'checked="checked"'; } ?>
id = "<?php echo $this->get_field_id( 'use_pinned' ); ?>"
name = "<?php echo $this->get_field_name( 'use_pinned' ); ?>"
<?php if ( isset( $instance['use_pinned'] ) && $instance['use_pinned']=='true' ) { echo 'value=true'; } else { echo 'value=false'; } ?>
type = "checkbox"
/>
<label for="<?php echo $this->get_field_id( 'use_pinned' ); ?>" ><?php _e( 'Exibir postagens fixadas no topo', textdomain ); ?></label>
</p>
I know it's probably very wrong, I was trying to get it to work but I'll leave it for later.
Still, please let me know if the version/plugin/theme info is valuable, so I can share it here.
Hi @fleig, Thanks for opening this ticket and taking the time to share the details.
I tried reproducing the issue based on the description, but I haven’t been able to observe the broken Widgets or Customizer behavior in my environment so far.
To help us investigate further and better understand what might be different in your setup, could you please share a few additional details?
Environment
Theme information
Plugins
Additional debugging information (if possible)
If you’re able to provide a screenshot or short screen recording of the broken UI, that would be especially helpful.
Thank you again for reporting this. The additional context will help us determine whether this is a WordPress core issue or something environment/theme/plugin specific.