Hi,

Please create a ticket regarding this on our support site and include your site url: https://support.vebto.com.

Thanks!

Hi, Finally I was able to set up R2 and got it working by following ChatGPT instructions. It was a steep learning curve but after spending a lot of time I was able to get it right. Beside that I have some other questions: 1, How to edit the footer? – In addition to “copyright” I want to add other links like “about”, “terms & conditions”... I can’t find the file location to edit it. 2. In the admin area I was able to implement alphabetical order for artists but in the front end it looks artists are shown based on who was added first, second… For example if you have a genre called Jazz and click on Jazz artists the artists are not showing alphabetically (Bemuisc puts the first added artist second, second added artist first and so on… and sometimes it looks random). How can I make Bemusic show artists alphabetically on the front end? 3, When users register with social accounts (Google, Twitter) and try to add password to their account Bemusic asks for current password that they didn’t create. It should not ask for a password that was not creatd – This needs an update. Thanks.

1. You can add menu items to it from “admin > appearance > menu manager” page.

2. You can edit the genre channel from “admin > channels” page and then select the ordering you want from there.

3. This will be fixed with next update.

Hi, for question #1, I was talking about the footer located at bottom of the landing page not menus. There is no footer section in the menus.

There should be a “Footer” and “Footer secondary” positions in the menu manager, are they not appearing?

Hi, I found them in the “menu positions” section. Where is the “Copyright © 2025 mysite, All Rights Reserved” located though? Is it somewhere in the site files?

Hi,

You should be able to change it from “admin > translations” page.

Hi, I’m not trying to translate it, I’m trying to edit it to some thing shorter like “©2025, mysite” instead of “Copyright © 2025 mysite, All Rights Reserved” This is the footer section I’m talking about: https://zefenic.com/pages/temporary-link

Hi,

Yes, you can test locally and then upload to live server.

Hi,

The spotify API changes only affect similar artists importing and automatically importing playlists made by spotify (importing playlists made by other users on spotify should work properly). We’re looking into alternative APIs for this, but no ETA for it yet.

Regarding performance, there should not be any changes between previous and current version. Are you seeing this issue on demo site as well?

Hi,

Thanks for your response and for clarifying the Spotify API issue. However, I want to emphasize that these are not just isolated issues or technical misunderstandings.

I personally reinstalled the script on two powerful VPS servers, fully equipped for high-volume use, and the same problems persist: search issues, Spotify API errors, and unstable performance. A colleague also reverted to the previous version, and everything worked perfectly — no Spotify issues, stable search, and smooth operation.

After closely inspecting the code, it’s clear the new version contains numerous deprecated elements, and while some can be disabled via .env, the Spotify API problems and other inconsistencies remain.

These are not just my observations or imagined issues. Multiple buyers in forums and private conversations share this frustration. The demo site might work fine in ideal conditions, but real-world usage exposes these problems.

I urge you to recognize the broader concerns and consider adapting the product to today’s evolving API landscape. Transparency, proactive communication, and timely updates are crucial if BeMusic is to maintain trust and keep pace with competitors.

Looking forward to your updates.

Which deprecated elements do you mean specifically?

Also, can you send a message via contact form here and include your site url, it’s hard to say what might be causing those issues without taking a look at the site. Nothing was changed in regards to spotify API in last update, so it should not have any effect on search or API functionality.

I am sharing a consolidated summary of the ongoing issues I have reported regarding the latest BeMusic script updates and Spotify API integration. This is to put everything on record clearly, as I’ve provided detailed information over many emails without satisfactory resolution.

Main Issues Experienced Frequent Spotify API errors including “Error … null” and HTTP 429 (rate limit exceeded) despite using a legitimate Spotify developer API key.

Inconsistent and unreliable search results — some tracks and artists appear intermittently or not at all.

Radio and similar artists functionality broken or severely delayed since last script update.

SQL deadlock errors during artist inserts: SQLSTATE: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction.

No built-in way to rescrape or reload thousands of artists and tracks after toggling deprecated API support.

The prior version of the script (which I have tested side-by-side) works perfectly with the same Spotify API keys and environment.

Many other users have reported similar issues, so it is not isolated to my setup.

The demo site and your provided API keys work fine but are not representative of real-world usage or updated environments.

Your own recommendation to use the developer API does not resolve the issues. (Also very limited)

Nulled versions of your script that use your API keys work without these problems, indicating the issues are in the recent official update’s code.

Despite my detailed feedback and multiple requests, no fix or rollback option is provided.

You confirm only the latest version is available on CodeCanyon, so reverting is not officially possible.

Additional Context:

You mention Spotify’s API changes after February 2025 affect some features, but the issues persist even with API keys created before that date.

I proposed potential workarounds (rotating client secret, toggling deprecated API usage) and provided logs for investigation, but the core problems remain.

The new update is significantly degrading user experience and causing errors that prevent a stable service.

Given the above, I consider this matter closed on my side. I will revert to the previous script version or explore alternative solutions unless an official update resolves these problems. I share this summary to keep an accurate and transparent record of my communications, and the nature of the issues encountered.

Thank you for your support.

I’ve looked into the two versions you mentioned and the spotify code between them is identical, there’s no reason that one should cause the issue.

If you send a message via contact form here with your site url, we can take a look if there’s some issue on the server or incompatibility with latest version.