5 months, 3 weeks ago #1056681
I noticed that with the latest update to Realty Portal, that the Yelp Nearby Places configuration page only ask for the API Key, as it should. (Reference my previous support thread titled "Yelp API has changed as of March 1st, 2018" for more info) I've enter my YELP API key and the feature is not working on my end. The only thing I see when I go to a property is the "WHAT'S NEARBY" title on the left and on the right it shows the "Powered by yelp!" Logo. Below that there is a horizontal rule then nothing below that and the page property description ends and goes to the perfectly OK footer. I've tried to to reset and request a new Yelp API key and still the 'Nearby Places' feature would not work. I then deactivate the new version (0.3.2) and activated the previous version (0.3.2.1) using the old Consumer Key, Consumer Secret, Token and Token Secret you supply in my previous thread about this issue, and everything works fine, as it did before the update.
Should this new version work out of the box? Is this an issue with the new plugin? Please, again, don't ask for access to my server, that unfortunately is not an option. Please help me fix this issue the best way you can.
Thank you.5 months, 2 weeks ago #1056697
BTW, I mess up on the versions in the above post. The new version of the Nearby Places plugin is in fact 0.3.3 and uses the new post March 1st API Key system. The 0.3.3 version of this plugin appears to not be working as described in the above post. The old version 0.3.2.1 DOES function correctly but using the old Key and Token combo system (Pre-March 1st, 2018). Just wanted to correct the version numbers I was speaking about so there was no confusion.5 months, 2 weeks ago #1056723
Thank you for contacting us and sorry for the late response.
Yes, we have updated the Landmark theme to fix the issue with Yelp API v2. Now it just needs one API key for Yelp config.
Please check it again.
Yes, you should update the latest version of all our plugin.
Jackie.5 months, 2 weeks ago #1056725
Thanks for contacting us.
We are so sorry for late response because we had a holiday from 28th to 1st so we cannot help you in that time.
For your question: In the newest version of Landmark theme, we updated API key following the new API Key of Yelp so you only create one key to use. The old keys cannot use.
Tracy - NooTheme5 months, 2 weeks ago #1056735
Ok, lets try this again. I've updated my version of nearby places to 0.3.3. I already had an NEW post March 1st, 2018 API KEY. (I'm aware the old system is gone) I've even reinstalled your theme from scratch and nearby places with version 0.3.3 IS NOT WORKING. I've attached an image showing what appears on my screen.
Could someone please help me out with this issue?
Attachments:You must be logged in to view attached files.5 months, 2 weeks ago #1056746
Thanks for your feedback.
Can you provide us with your website's URL and admin account privately?
We want to access your website directly to check this issue.
Tracy - NooTheme5 months, 2 weeks ago #10567605 months, 2 weeks ago #1056818
Please check your site again. We can't access your site to help you check the issue.
It response the error Fatal error: Call to undefined function define() in C:\Internet\http\themes\landmark\index.php on line 14
Jackie.5 months, 2 weeks ago #1056819
Ok try it again. Not sure why that happened but it should be working now.
Thanks.5 months, 2 weeks ago #1056843
Can you give us the FTP account? We need to debug the source code. We try to help you change the Yelp API key but it doesn't work.
Please give us your FTP info.
Jackie.5 months, 2 weeks ago #10568495 months, 2 weeks ago #10568515 months, 2 weeks ago #10568525 months, 1 week ago #1056977
Is there an ETA for this issue, it's been 5 days since I last heard anything, anyone?5 months, 1 week ago #1056996
Thanks for your feedback.
Our developers are checking your website but we haven't found the issue yet.
Please wait for us, we will try to feedback you soon.
NooTheme5 months, 1 week ago #1057141
At this point we are going on two weeks, and no fix. While I appreciate your effort, I am growing more and more frustrated and here is why:
When I initially spoke about this issue I explain CLEARLY that I was using 0.3.2.1 version of Nearby Places, as the 0.3.3 NEW version would not work when I installed it on a fresh install of the Landmark Theme. Therefore, considering this was a PRODUCTION SITE, it was VERY IMPORTANT THAT 0.3.2.1 CONTINUED TO FUNCTION until a fix was in place. Within hours of me making these statements in your support forums someone in your team, disabled my ability to continue to use the 0.3.2.1 version, as they disabled the Yelp Key/Token combo you guys sent me in another support post and therefore I could not use the plugin at all. A plugin I explained initially was one of the MAIN FEATURES we were depending on when we purchased the Landmark Theme.
Here is my initial support requesting proving my claim:
So my questions are:
1) Why did you disable the old method of accessing nearby places when many people were using this feature in a production environment and why was the old KEY/TOKEN method disabled done hours after I explained I was using the older key/token combo YOU HAD GIVEN ME???
2) Can you re-enable the Key/Token that you previously gave me so ON MY PRODUCTION SITE I can at least have SOME WORKING VERSION of the Nearby Places plugin until a fix is issued???
In closing, your actions are harming my clients ability to do business and you are causing both of our companies financial harm. You shouldn't have disabled the old KEY/TOKEN method of Nearby Places only hours after you updated the plugin to 0.3.3. What happens when someone can't get the new version to work LIKE ME, basically in that scenario the people that purchased your theme are screwed with NO WORKING VERSION OF NEARBY PLACES ON THEIR PRODUCTION SITES. I guess I should be thankful the THEME CORE is still working after the update, otherwise I'd be without A WORKING SITE AT ALL FOR 2 WEEKS NOW!
Please help me with SOME KIND OF TEMP FIX!!!5 months, 1 week ago #1057190
Yes, we have updated the Yelp API V3, on the API v3, it doesn't use the Key/ Token as the old version. On the V3 API key, it just using one API key. That is why we need to change.
And we are trying to fix the issue with Yelp API V3, please give us some days. We will let you know soon.
Once again, sorry for the late.
You must be logged in and have valid license to reply to this topic.