Tonya Mork

All links is not working, even images with links does not function, used to work before. I’m using Elementor. My theme is ocean.

@jasleth I’d suggest opening a new support request for the issue you’re seeing, as this support thread is not related to that issue.

Hello all,

WordPress 6.6.1 is released and now available https://www.ads-software.com/news/2024/07/wordpress-6-6-1-maintenance-release/. It includes the fix to the “all links underlined” issue reported in this support thread. Thank you everyone.

I was able to test the supplied Gutenburg plugin test (vers 18.5.0-rc.1). After install the underlining issue?appears to be fixed!?I’m also not currently noticing any new problems created by it yet.

That’s great news @jsko40. Thank you for testing the proposed fix ??

Also, I added your test report to the WordPress Core Trac ticket.

WordPress does say there is the 18.8.0 version of the plugin available. Should I also upgrade to that and test that? Or just go ahead and wait until wordpress 6.6.1 is available since I don’t typically have a separate Gutenburg installed? I can also utilize the workaround css supplied by Divi until then.

Until 6.6.1 is released, you can choose the option that works best for you: upgrade to the newest version of the Gutenberg plugin, use the Divi workaround, or wait for 6.6.1. If not upgrading the plugin, it can be deactivated and removed from site.

I appreciate your frustrations.

The pause in releasing the proposed fix in 6.6.1 is due needing feedback. Need to know if the proposed fix does indeed fix the issue on affected sites.

This where folks affected by the issue can help. That said, I appreciate that not everyone affected is able to help test it (for whatever reason).

Thank you reporting the issue and for your patience.

Hello @daphnetalbot,

What is the ETA for the version release?

The status right now: need to validate the proposed fix before scheduling 6.6.1 release. Why? To ensure the fix does indeed resolve the issue and without side effects.

A good way to find out is to test the fix on affected sites. A test plugin is available with the proposed fix. It’s a plugin that can be downloaded, unzipped, and installed/activated on an affected site. Then when done testing, it can be removed from the site.

Are you able to test the fix (which is an installable plugin) on one or more of the sites you manage? Details are here:

If possible, appreciate you testing the fix (which is available in plugin format) and giving feedback if it resolves the issue you’re experiencing. How? Details are found here?https://core.trac.www.ads-software.com/ticket/61660#comment:16.

Hello @rdiebel @hoenens @sishorif @jsko40,

The issue has been reported and is being tracked in this WordPress Core Trac ticket https://core.trac.www.ads-software.com/ticket/61660. A fix is identified and ready for testing.

If possible, appreciate you testing the fix (which is available in plugin format) and giving feedback if it resolves the issue you’re experiencing. How? Details are found here https://core.trac.www.ads-software.com/ticket/61660#comment:16.

Hello,

Thank you for your report. This issue is reported and known in WordPress Core Trac https://core.trac.www.ads-software.com/ticket/61660. This issue appears to be fixed in Gutenberg and is planned for 6.6.1. I invite you to track and, if you’re interested, help test in the Trac ticket.

• This reply was modified 8 months, 2 weeks ago by Tonya Mork. Reason: fixed typo

Thank you @pauthake015 for confirming the issue was fixed in your testing ??

Hello @steadyup,

This is a new file in 6.1.

Fatal error: require_once(): Failed opening required ‘/home/tdusjuf1zkmi/public_html/wp-includes/class-wp-textdomain-registry.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in /home/tdusjuf1zkmi/public_html/wp-settings.php on line 155

What is this error? In wp-settings.php on line 155, there’s a line of code that loads wp-includes/class-wp-textdomain-registry.php into memory. The fatal error happens when either that file does not exist or the file is not loadable.

Looking at the Warning message,

Warning: require_once(/home/tdusjuf1zkmi/public_html/wp-includes/class-wp-textdomain-registry.php): failed to open stream: No such file or directory in /home/tdusjuf1zkmi/public_html/wp-settings.php on line 155

it’s alerting that the file does not exist.

What can you do?

You could check if this file exists and if it’s readable (check it’s permissions).

If it’s not there, it’s possible the update was incomplete. And if yes, then it’s also possible that other files may also be affected. A manual update as @t-p noted could resolve it.

You’re right, it likely is a configuration error. I’m assuming you’re using Method I https://www.ads-software.com/support/article/giving-wordpress-its-own-directory/#method-i-without-url-change.

In a quick review, there are differences between the .htaccess file you posted above and what is recommended in the support article. Maybe a side-by-side comparison could help.

Hello @jlspeers,

The images are not showing and give a 404 error. I see WordPress is installed in a subdirectory.

This article, “Giving WordPress Its Own Directory” https://www.ads-software.com/support/article/giving-wordpress-its-own-directory/, can help you in setting up the subdirectory.

Hello @styryou,

I’m sorry you’re having issues with that plugin after updating.

Looking at their demo site, it too runs on WP 6.1 and is experiencing the same filtering issue you noted.

Without diving into their premium product, it’s difficult to assess the root cause. Forum volunteers do not have access to premium / commercial products; so we would not know why it’s not working correctly. It is possible other community members may have faced your issue and may possibly be able to help you.

Your best bet is to contact (which you did) and work with the plugin’s developer.

Added benefits of using the official support venues: allows the developers to be aware of issues with their code and gives back to the community in a more robust way.

• This reply was modified 2 years, 4 months ago by Tonya Mork.

Hello @pgmelton,

Sorry for the delay in someone responding to you.

I’m not aware of books that specifically cover WP 6.0. However, Learn WordPress might be beneficial for your students and you.

Cheers,
Tonya

Hello @ace0930,

Appears the function named function_name() is located in the global namespace, rather than in the test namespace.

How to find out:

• Locate where the function exists in the code.
• Scroll to the top of that file.
• Is the test namespace defined in that file?

The PHP manual has some examples to help you.

WooHoo, I’m glad you found the plugin and now the widgets screen is working again for you.

The next step could be reaching out to the plugin author(s) to alert them to the issue you were having by reporting it here https://www.ads-software.com/support/plugin/visual-form-builder/.

I’ll go ahead and mark this issue as resolved as it’s not due to Classic Widgets plugin.

Thanks for working with me on figuring out the problem. Cheers.