ceophoetography

Thank you.

So, after preparing an e-mail to explain to my web host why they should upgrade, I found no method of sending the e-mail and wound up using their on-line support chat. And the support person showed me that I could update PHP, even to 7.1, using the control panel.

While I still don’t care for the sledgehammer approach Yoast used, it was effective.

Thank you for the link; that’s good information. However, it’s very poor public relations to make me unable to dismiss the notice once I’ve read it. I mean, I don’t care if you make the notice appear every time I log in to the administrative page, but at least let me acknowledge it and get it out of the way. I just want to be able to dismiss the notice, not ignore it. I think it’s wrong of Yoast’s developers to make the administrators’ dashboard fit the Yoast agenda more so than the work the administrator is trying to accomplish.

Okay, I get it! I need to try to get my host to upgrade to PHP 5.6, at minimum, but it will take time and there are other concerns to address. Why shouldn’t I be able to acknowledge that I’ve read the prompt/warning today and suppress it for today? What give Yoast’s developers the right to be obnoxious?

I guess I will have to roll back my version of Yoast and/or deactivate the Yoast plugin.

For the next step in my cyber-detective work, I’ve deactivated all of my plugins except for Maintenance Mode (so that I can have the site in maintenance mode while I go through all of this), Pretty Link, and SNAP. I deactivate Pretty Link to see if it triggers the 500. It does not. So then I add additional active plugins until I can figure out which third plugin contributes to the conflict.

I’ve done some experimenting. With Pretty Link active, I could activate the NextScripts Social Networks Auto Poster (SNAP) plugin; I would only get the 500 if I then deactivated the Pretty Link plugin. With SNAP inactivated, I was able to deactivate Pretty Link with no problem. I was able to deactivate a different plugin with SNAP active. Bizarre.

The problem appears to be a (sudden) plugin conflict. I don’t know if Pretty Link is even involved. As renaming the plugins folder did nothing, I had to use phpMyAdmin to disable all of the plugins. I’ve been reactivating them one at a time to try to locate the offender.

I have looked at the CGI errors log, which seems to suggest that the Social Networks Auto Poster plugin may be the culprit. That’s one that’s back-end only. I would think that any plugin that affects the front end would knock out the website as well as the administrative end.

I was in the plugin screen, and when I clicked “Deactivate” under Pretty Link, I got an Internal Server error and haven’t been able to access wp-admin at all. My server log hasn’t been updated/modified since 2014. I tried renaming the plugins folder and the pretty-link folder. Neither was successful in restoring administrative access.

Use FTP to rename or delete the “feed-them-social” folder (inside wp-content/plugins) and then refresh your admin page. The FTS plugin is apparently broken.

Thank you, David, for all of your wonderful assistance. Using your code above as a starting point and consulting the documentation (as I’d been doing before posting here), I was able to get everything working the way I envisioned.

<?php echo do_shortcode('[mla_tag_cloud mla_output=flat taxonomy=attachment_tag post_mime_type=image ids=' . get_the_ID() . ' largest=11 smallest=11 unit=px mla_link_href="' . esc_url( home_url( "/" ) ) . 'exhibiting-peace-offering/?current_item={+term_id+}&tax_input{{+query:taxonomy+}}{}={+slug+}&muie_per_page={+template:({+request:muie_per_page+}|20)+}" mla_rollover_text="Click to view more &quot;{+name+}&quot; photos"]' ); ?>

It did not require the use of sprintf() at all.

Thank you for your response.

If I code an ID into my template file (image.php), then how will be able to specify for each attachment? If I have 1,000 attachments, then I need for MLA to “read” its ID or slug and build its tag cloud from the attachment tags for the tag in question. Basically, I need a dynamic application: each time that an attachment is opened, I want a tag cloud of that attachment’s terms to appear. Is there a way of doing that?

As for the breaking of tag styles, I guess I’ll just have to figure out, based on my style sheet, the exact number of ems to assign the shortcode (as well as assigning a unit of em instead of pt or px). The way that it’s breaking is that the :before is not the same size as the link. Right now it’s just on my test server.

The solutions you gave me work fabulously, David! They make my searchable gallery page look just the way I want. I have a small random tag cloud at the top of the page to provide users with ideas about what my collection contains, then a search form, the gallery, and a larger tag cloud of my most frequently used tags at the bottom of the content.

The only problem is that I am unable to use muie_keyword_search mla_search_connector='OR' successfully. I’ve tried mapping the taxonomy terms of my (test-site) attachments using 2#025 keywords, but my shortcode still delivers no results. I’m using muie_terms_search mla_terms_taxonomies=attachment_tag successfully, but I wonder if that will limit my end users’ results when they enter phrases that only partially match one or more attachment tags.

Great work, sir!

P.S.: When you get a chance, you might want to look at the User Notes section, #4, of the MLA-UI-Elements-Example plugin. [muie_per_page] appears twice, but the second time it should probably be [muie_keyword_search].

Edit to the previous post:

My mistake: It works completely. I had forgotten to update the MLA version on the server when I tested the live version, and that’s why the links didn’t show.

Many thanks, David!

He’s working on that. See this recent post that he’s helping me with:

Limiting search results to attachment tags.

It works! Yay! Thanks so much.

No navigation appears beneath unattached images (viewed from the media library), but the main thing is that the page is whole.

Thank you for all of the work you’ve put in. I installed the latest development version on my localhost test site and tried an image with the code you supplied.

It almost works. The only problem is that instead of the link text, the output is the thumbnail of the image. The mla_output parameter appears to be ignored.