HabD

Okay, I got it! Found it! Sorry! On the very dar right side I now saw the option to set (bot on the option page…). Sorry, my blind eyes! Any yes, not all works the best!

Also without (both) backslashes it does not work! And there are still the two hints (in German):

• Remember to enable the Regular Expression option if it is a regular expression.
• Your target URL contains the invalid character % (invalid)

Currently I really do not get the point what is not working… Will say: Help is super-welcome!

Thnx!

Okay, my initial question is solved – as I mingled “POST” with “GET”… So, all works!

Hi, so would appreciate it if someone could set an option to “always“ or ?manually“ delete a post on the remote synchronised site whenever someone deletes a post on the source site!

Hi Jory, thanks for bringing this up on GitHub. Hope to see this solved.

thanks for caring about my request. But it does not describe what I wanted to ask for. It is:

I use the relationship to create a list of options like:

Apples, carrots, oranges, bananas

And I want to set the parameters of the custom field in a way that for any new post e.g. carrots and bananas are already set (as default values).

in the regarding option of the CF I can set only one value to get set as default. But I did not manage to set more than one. I tried a comma-separated list nut this did not work.

any ideas?

Hi Scott,

Well, I just created a new CPT and did not change much from the default settings. But maybe, one of the tiny changes may have caused this.

As I am just starting to get familiar with Pods (to find out if I shall change from Toolset to Pods as Pods is better supported by Dynamic.ooo than Toolset regarding grabbing related articles between a CPT and regular posts …) I was able to delete the CPT (and used the Pods admin settings to delete all related data, good functionality!)

I tried a new CPT –?and now all works! So, though I compared to non-working CPT with this new one I was not able to find out which setting made the difference.

But now works – and maybe I will find out what caused the problem when tinkering around a bit further.

Thanks so far!

Kind regards, Martin

Dear Stefan,

Thanks for checking it out at least! I understand that you cannot support all plugins – and follow their changes… anyway, very kind that you had a look at it!

And as I write: let me express my deep appreciation for Admin Columns. It is such a useful add-on that au use a lot, especially for better searching via custom post fields and editing the found set afterwards.

Kind regards, Martin

Thanks for your fast reply. The sender address was already verified by Mailpoet in my account. But now after trying it again, it got accepted. So, though it now not initially for whatever reason it now does work..

Okay, I found a free way to do so – and just added a few lines to the code of the plug-in. As the custom post field is provided in the $post variable it is easier than I thought.

Okay, thanks for the info. Any hope to get this checked by the plugin? Just as an “error” is alarming. Just as if you start to ignore it (as in my case I am currently replacing missing image with a backup) you will one day miss the case when an error message is relevant…

Dear Sweta,

No, no I habe not. Where can I do so? I‘d like to help as this helps the plugin and me, too. Because of the error I had to skip the plugin and have to wait for a fix of the bug…

Kind regards, Martin