jfbprivate

“Ignore all query parameters” would actually do the opposite of what I need it to do.

Anyway, I got it working now. “Exact match in any order” was the correct setting, but I had to uncheck the “Ignore Slash” option. I had tried that earlier and it didn’t work then. Might have been a caching issue.

Thank you.

Thanks for your response and apologies for the late reply.

I think I can live with that. I noticed that even Wikipedia has the quotes outside the title link.

There is one last issue however. The page titles for titles that need to be italicized are in the following format which works well all throughout WordPress:

<em>New Title</em>

This will display them correctly on both the actual pages and index pages of Yada Wiki, TOC being the exception.

The TOC page somehow doesn’t recognize them as existing pages. Could that be caused by the HTML in the titles? Interestingly that is not an issue anywhere else. The HTML bits are being ignored on all other pages.

I’ve tried the following but the links show up as not-yet-existing pages:

[yadawiki link="New Title" show=""]

[yadawiki link="<em>New Title</em>" show=""]

Any idea what might be causing this or why the TOC page is behaving differently from the rest of the wiki?

Thanks again!

Thanks for the quick response.

The documentation doesn’t really mention the case. I have tried all these options but they’re not working for me.

I quote, “For example, if your source URL is /my-old-post and your target URL is /my-new-post, and the user requests /my-old-post?tracking=1 then the redirected URL will be /my-new-post?tracking=1“

That is exactly what I don’t want.

I need /checkout/ to redirect to /account/. And /checkout/ only. For example, I need /checkout/?item=1 to be excluded from the rule.

However, in your example above this would redirect to /account/?item=1 instead, which is what I don’t want since it would break the link.

The idea is that users are not supposed to access /checkout/ itself. The same is true for /confirmation/. These pages don’t make sense without their respective query parameters.

Thanks again.

• This reply was modified 5 months, 1 week ago by jfbprivate.

PS: I forgot to mention that I was referring to the TOC page and other lists.

Setting up an index table via [yadawiki-index type=”pages” columns=”4″], on the other hand, all pages with titles in the form of ‘<em>This Is a Title</em>’ will both display italicized and work as links correctly.

Thanks for the quick response.

This is a working solution using HTML:

[yadawiki link="This Is a Title" show=""This Is a Title""]

Now, similarly to using quotation marks for some titles, I’ll have to italicize others. The problem with that is that <em> seems to be ignored in both ‘link’ and ‘show.’

Wrapping the entire shortcode in <em> would work:

<em>[yadawiki link="This Is a Title" show=""]</em>

However, I also need the page title to be italicized, which means that the Yada link would no longer be “This Is a Title” but “<em>This Is a Title</em>” since that’s what the actual page title would be now. That brings up another issue because Yada Wiki won’t accept <em> as part of a link and will turn it into a ‘wikilink-no-edit.’

If the plugin would accept HTML in page titles, I could make it work like in the following:

[yadawiki link="<em>This Is a Title</em>" show=""]

As mentioned above, I have also tried using <em> in ‘show’ but that is being ignored too:

[yadawiki link="This Is a Title" show="<em>This Is a Title</em>"]

In order to make it work like in the above example, the plugin should IGNORE the HTML in the page title (‘link’) and ACCEPT the HTML in the ‘show’ part. That would probably be the most straightforward solution. I’m actually surprised that it does accept ‘&quot;’ but not <em>.

I feel like especially a wiki should be capable of styling titles properly. Am I missing something?

Thanks again for looking into this!

Hi,

Replacing those lines seems to have fixed that particular issue.

I’ve come across some other (related) problems however.

================

Instead of what is set in the plugin I’m getting the default BuddyBoss/BuddyPress error messages for the following scenarios:

Username too short:
[1 character] = “Username must be at least 3 characters” (BuddyBoss)
[2 characters] = “Username must be at least 3 characters” (BuddyBoss)
[3 characters] = “Username must be at least 5 characters.” (plugin)
[4 characters] = “Username must be at least 5 characters.” (plugin)

Username too long:
[16 characters] = “Username may not be longer than 15 characters.” (plugin)
[32 characters] = “Username may not be longer than 15 characters.” (plugin)
[33 characters] = “Username must be shorter than 32 characters.” (BuddyBoss)
[34 characters] = “Username must be shorter than 32 characters.” (BuddyBoss)

Username empty:
[0 characters] = “This is a required field.” (BuddyBoss)

================

Here are more but I realized that there are no options for name and empty password fields in the plugin, even though that would actually be a useful addition.

Name too long:
[33 characters] = “Name must be shorter than 32 characters.” (BuddyBoss)
[34 characters] = “Name must be shorter than 32 characters.” (BuddyBoss)

Name empty:
[0 characters] = “This is a required field.” (BuddyBoss)

Password empty:
[0 characters] = “Please make sure to enter your password.” (BuddyBoss)
[0 characters] = “Please make sure to enter your password twice.” (BuddyBoss)

================

At least in the case of BuddyBoss/BuddyPress the plugin doesn’t seem to successfully overwrite the default error messages.

In fact only the email field seems to be working correctly for both empty and existing values.

I would very much appreciate if you could look into this. I can’t be the only one having these issues.

Thank you!

Thank you for looking into this. Your help is much appreciated. Looking forward to the new release.

I did some more testing and it’s actually BuddyBoss Platform itself that is causing the issue. Once deactivated the correct error message will show. We will have to look into this with their support team.

Please let me know if you should come up with anything in the meantime.

Thanks much!

Thanks for the quick response.

I forgot to mention that this is not the case. Otherwise I wouldn’t have started this thread.

Let’s say I set the length to a minimum of 3 and a maximum of 24 and then try a 10-letter username without any special characters whatsoever, it will still return the invalid character error message.

I should also mention that this is a BuddyBoss install which already overrides some of the error messages defined in the plugin.

I’m 100% sure that this used to work correctly before though.

Thanks much Lap!

Or, if easier for some reason, the other way around:

I could change the actual value from “1990” to “Year 1990” but have it output as “1990” in the frontend.

Whatever works best.

Hi @mrdaro,

I appreciate the detailed response here.

No need to figure it out really, but it actually makes me wonder why and how the success page is still working without using the shortcode.

Thanks again!

Hi @mrdaro,

Thanks for the clarification.

So basically you’re saying that all shortcodes that would also be available from the Dashboard are optional. You also state that the Confirmation page is necessary and must include the receipt shortcode. However, I am not using the shortcode and the receipt is showing just fine. On your website it also says the following:

“If you use our Legacy form template, your donors want to confidently see confirmation that the donation they submitted was successful. Reiterating and displaying what they donated is a confirmation that you collected the proper information. Without this shortcode, your donors will not see a confirmation of their donation or important information about their donation history.”

Since I am using the multi-step form it seems I can ignore it. Am I missing something?

And one last thing: Is the Failure page required or not?

Thanks much again!

Nothing?

So I purchased the plugin three days ago but instead of being able to create more than four clocks I am no longer able to create a clock at all. The menu to set them just disappeared. It also caused a critical error on the site. Since it’s the paid version it’s probably no longer a WordPress forums discussion. But we need to figure it out one way or another. Please get back to me ASAP. Thanks.