Douglas "BearlyDoug" Hazard

Good morning, miniOrange teamies!

I actually updated the day you released it (appears to be the 14th), hah!

Looking forward to integrating it… AND to paying for the pro version. ??

Thank you for getting this addressed. ??

On the front part of the site, we only have guest access. While we use UAM to control who has access to what departments/features within WP-Admin, on the front side, we don’t limit that (except the Extranet/Intranet, which is not tied to the search stuff).

There are no other hooks (aside from the one I did) within the theme’s functions.php file for RelevanSSI.

When I rebuilt the search index (tested on our dev site AND live site) and after the appropriate code was put into functions.php, the three results I expected to NOT see went away after the rebuild. I had made other changes (unsuccessfully), and reverted them back prior to finding the solution that did the fixes correctly.

(I eat, breathe and sleep PHP/WP development… it’s a full time salaried gig for me, so I’m a bit more “creative” than the casual WP user.)

Good morning, Mikko! Apologies for not clarifying this… this is on the front side. I think I know what happened, though.

At one point, these items were published as news and slider items, however, when a certain issue came to light, our communications department (along with our legal team) decided it would be in the best interest of the Organization to pull these items off the site, publicly.

Since they had already been indexed by RelevanSSI, the links/search results (publicly) were still available, despite being pulled back into draft status.

This actually leads me to my next suggestion: Is there a maintenance task RelevanSSI can “tap” into (WP Cron) to make sure that when post statuses get changed, indexes get updated, correctly?

(I’d be happy to share the site/organization with the RelevanSSI team, privately, if requested. This might help explain a little more about the issue I faced.)

Okay, so I actually found a workaround for this, thanks to both @msaari’s post in THIS THREAD, and then re-building my search index.

IMHO, you need to be able to pick posts/page status within the settings under Indexing.

Thanks!

• This reply was modified 5 years, 1 month ago by Douglas "BearlyDoug" Hazard.

I humbly apologize… all of these issues were 100% self inflicted…

When an HTML tag is present (especially in a link), TP (correctly) tries to have you translate each string of text separately (green arrow).

I changed each nav link section so I could edit/translate the entire section at one time.

Turns out that when I copied the ENGLISH version of the text, it also copied every component of that <.a> tag, including link targets and specific URLs… so everything was being hard-coded.

I took out all the extra stuff and set the links to what I was EXPECTING them to be, and voila! It works!

Marking this resolved, but hoping this stays up, so others don’t have a colossal brain fart like I did.

• This reply was modified 5 years, 1 month ago by Douglas "BearlyDoug" Hazard.
• This reply was modified 5 years, 1 month ago by Douglas "BearlyDoug" Hazard.

Just found another bug…

On the normal (English) version of the site, three of our five navigation menu items are set to open those links in a new page (they link to a different domain, completely)

When I’m on the Spanish version of the site, those links do not open in a new window.

There is absolutely something hinky going on… and we need a resolution, quickly. I have senior management breathing down my neck on this. There are press releases and a press conference centered around all of this.

Thanks.

No. I still cannot click to other slides while the current slide is in motion.

Done. ??

You’re still missing my point… even AFTER the first animation is done moving… I cannot click the dots/arrows until *any* animation is done moving.

Yours is the only slider where I’ve seen this happen (both WP and non WP) in the 20+ years I’ve been doing web development. ??

Even with the interval dropped down to 100, I still cannot click on the dots to go back or forth until the slide, itself, has stopped moving.

FYI, no javascript errors are being reported (I made sure to check that, as well).

I hope so, as well, @christinahills. ??

Even though I may be done with *this* plugin, I’m working on getting approval from my NEW job to release a new plugin. Lots of politics (I work for one of the largest organizations in the world, now) and hoops to jump through, though, haha!

Christina, go ahead and go back to the original plugin. It appears they’ve got an update released… hopefully he fixed the same bugs I initially did.

Just deactivate the rw version, and activate the updated QPPR plugin… should be a *very* smooth transition.

All due respect, @anadnet, but the last update was over three years ago. There are several bugs that needed to be addressed. I even reached out to you (via my old work email address) and other methods (including Social Media) to try to get your attention.

There’s even a warning on the top of the main plugin page that this hasn’t even been tested with the last three versions… and with the huge change in how WP’s posts/page editor layout changed (Gutenberg), this plugin wasn’t updated to factor that in.

I would LOVE to see an update by you, with the bug fixes needed, and WordPress 5.x compatible.

This is one of my favorite plugins to use, but with no development/updates/support in 3+ years, people were getting frustrated.

If you CAN get this updated, frequently maintained AND provide proper support, I’ll be happy to pull my version back down and refer people back over here. I would rather the original author/plugin be put to good use. ??

@manakuke, I also came across that issue, as well (before filing this report). I didn’t want to “piggyback” onto that thread though, in case anyone else was having a similar issue.

I will probably submit a “nudge” ticket in through the official support methods to ask them to review this. Since this is the defacto plugin we’re using “officially” for the Richmond Diocese (140+ churches; 180+ sites), it’s imperative this bug gets fixed correctly… and quickly. ??

Custom CSS will do that:

.textwidget .ai1ec-views-dropdown {
        display: none;
}

.textwidget .ai1ec-btn-toolbar {
        display: none;
}

.textwidget .ai1ec-pull-left {
        display: none;
}