Hi there, @destmedia,
To modify the a href attribute for the images to include rel=”nofollow”, you will actually not find this within template files, as it is typically added through filters or actions in the plugin’s code. However, directly altering the plugin’s files is not recommended because your changes would be lost with every update.
Instead, you should use WordPress hooks to add attributes to your links. For example, you can use the wp_get_attachment_link filter to add a rel="nofollow" attribute to your gallery images.
As this involves writing custom code, which falls outside of the scope of support we offer, you might want to get in touch with a developer or use a child theme’s functions.php file to implement the necessary changes safely.
Please note that modifying the HTML output can sometimes lead to unexpected behaviour or conflicts with other plugins, particularly those related to SEO or caching. Be sure to test any changes thoroughly.
Hope that helps! Semi-related: I checked your Jetpack connection, and it doesn’t seem to be working at the moment due to a block on your server’s end. You may want to report this to your host, and check for any security/caching plugins you may have enabled, and try temporarily disabling them to see if it fixes the problem. You may also want to search for any firewall on your server side that might be blocking the communication with the xmlrpc.php file – your host should be able to help you with that.
Please let me know if you have any further questions or doubts about the above. Thanks!
Dear Stef,
Thank you for your extensive response. I indeed found the appropriate filter you mention. As the filter didn`t want to listen i got fed up and just de-attached the media files of all my galleries via wp cms. Took 5 minutes. Could be caused by same caching issue, come to think of it..</p>
<p class=””>I`ll look into the xmlrpc file, see how that effects my results. Always great to learn something..!
Gracias.
Stef.. Looking into the xmlrpc: For my personal use i assume it can remain disabled. You figure jetpack needs it somehow though ?
Hi there, @destmedia,
Glad to hear you eventually found a way to work out the media – hope it’s a good solution for you even if not what you planned.
As for the XMLRPC file, yes, Jetpack needs that to connect to your site unless your host features an alternate endpoint. I see that the connection looks solid, so I’d recommend keeping the xmlrpc file enabled if you can 🙂
Please feel free to reach out if you have any other questions or need some more help!
