wci

ok – thanks.
I found now the corresponding usable codes in Geodirectory > Notifications > Options

List of usable shortcodes:
[#client_name#],
[#listing_link#],
[#posted_date#],
[#number_of_days#],
[#number_of_grace_days#],
[#login_url#],
[#username#],
[#user_email#],
[#site_name_url#],
[#renew_link#],
[#post_id#],
[#site_name#],
[#from_email#](in most cases this will be the admin email,
except for popup forms)

Best, Alex

Hi Alex,

you have all the details above in the ticket

Using the add listing URL and implement i.e. this link > https://www.yelp.com/biz/cosa-bella-salon-and-day-spa-houston

Ftp will be sent in private message.

Best, Alex

Just for info:
Yelp API : https://www.yelp.co.uk/developers/documentation/v3/authentication#where-is-my-client-secret-going

Where did my client secret go?
Prior to December 7, 2017 the API used OAuth 2.0 to authenticate requests to the API. In an effort to simplify authentication, starting March 1, 2018 the API no longer uses OAuth 2.0 for requests and moved over to only API Keys.

With OAuth 2.0 the process to authenticate was:

Get your Client ID and client secret from the Manage App page.
Make a request to the token endpoint with your Client ID and client secret to get an access token.
Put the access token inside of the request header as “Authorization: Bearer <YOUR ACCESS TOKEN>” and make requests against the API.
With just API Keys the process to authenticate is:

Get your API Key from the Manage App page.
Put the API Key in the request header as “Authorization: Bearer <YOUR API KEY>”.
And that’s it! You no longer need to make a request to the token endpoint to get an access token. Your API Key does not expire like the access tokens used to, so you don’t need to worry about generating new ones. Note that the API Key is not a drop in replacement for the client secret. Using the API Key as a client secret in the token endpoint will not work.

Migrating your app to use API Keys
For both OAuth 2.0 and API Keys the authorization header structure is exactly the same. Your previously generated access token has automatically been converted to be your non-expiring API Key. What you need to do depends on how you authenticated:

If you were caching your access tokens, the only change you need to make is to remove the call to the old token endpoint. Everything else should work seamlessly.
If you were making a request to the token endpoint for every API request, you need to remove the intermediary request to the token endpoint and store your API Key in your app. Use the API Key in the same place you were using the access token returned by the token endpoint.

Hi again,

I have checked about the 2nd Problem “http 500 error” which is related to the SNAP plugin from nextscripts. After dropping in plugins_off folder this problem is solved. I have contacted the SNAP support to get help.

So only the 1st problem is still open to solve. (I guess it is the yelp API change to be aware of and the solution from your end is still open to develop).

undefined error
Using the add listing URL and implement i.e. this link > https://www.yelp.com/biz/cosa-bella-salon-and-day-spa-houston then I am getting an undefined error.
Screenshot > https://www.screencast.com/t/F3hcX2qacGjC

Best, Alex

Hi Alex,

thanks for respond. Well I do not know why or where these old URL data comes from, as the listings were created with the right proper country > city location selected and then been saved.

Right after the saving then the auto submit from SNAP plugin takes place and there are wrong URL data used at the submission for what ever reason.

I thought this might has anything to do with formerly old main city settings done, but as we use the gd multilocations plugin I cannot find anything wrong set.

YES, the SNAP support is also informed, but still got no info so far.

May you also have an other idea to submit again to SNAP for their investigation.

Best, Alex