Home / Page 2

B

Forum Replies Created

Viewing 17 posts - 26 through 42 (of 42 total)
1 2
May 14, 2020 at 7:50 am in reply to: After upgrading to WP 5.4 /wp-json/wpdm/v1/packages gives 404 #128254

B
Participant

Hi,

Thank you for the screenshot. We had only checked the statuses within the “Download” tab itself, not in the “Plugins” tab. We found out that only the super-user was able to see “Download Manager” and “WPDM – REST API 1.2.0” in the list of plugins. Other admin users only saw “WPDM – REST API 1.1.0”.

After some digging in the support forums, the person responsible for our WordPress installation found a post from 2013 regarding multi-site vs single-site. After deactivating multi-site, and completely removing the 1.1.0 REST API plugin, the correct plugins were visible for other admin users, and the same users were once again able to use the API.

Thanks for the assistance! ๐Ÿ™‚

May 12, 2020 at 7:44 am in reply to: After upgrading to WP 5.4 /wp-json/wpdm/v1/packages gives 404 #128091

B
Participant

Hi,

We did not get any fatal errors when installing, and we cannot see any indications now that the installation was unsuccessful. We did exactly what you described in a previous post, so the procedure should be correct as well.

I am starting to suspect that you might be logging into the original creator of this thread’s website, and not ours. We had a similar issue, so I posted in this thread, but our credentials are posted further down in the thread history.

I have 3 questions, could you please address them all?

1. Are you sure that you are logging in to the correct website?
2. Should I create a new thread on this issue such that we are the creators of the thread?
3. Could you please tell me were you get your information on WPDM, WPDM API status? We have never seen the same information/status as you, so we really want to know were you get yours

May 11, 2020 at 7:55 am in reply to: After upgrading to WP 5.4 /wp-json/wpdm/v1/packages gives 404 #127990

B
Participant

Hi,

Could you have another look, and answer the question “Where did it say that the version was 1.1 (and previously that the add-on was not installed)?”. Since you didn’t see that the addon was installed the first time, and after we upgraded to 1.2 you found 1.1, we are probably checking for the addon status in different places. See reply #127432 for details on where we are looking.

May 4, 2020 at 8:54 am in reply to: After upgrading to WP 5.4 /wp-json/wpdm/v1/packages gives 404 #127436

B
Participant

Hi,

This is what we just did, but it still does not work.

How about the first question: “Where did it say that the version was 1.1 (and previously that the add-on was not installed)?”

Could you have another look now that wpdm is 5.0.8 and the REST API is 1.2.0?

May 4, 2020 at 7:40 am in reply to: After upgrading to WP 5.4 /wp-json/wpdm/v1/packages gives 404 #127432

B
Participant

That is very weird

Where did it say that the version was 1.1 (and previously that the add-on was not installed)?

If I look at wp-admin->Downloads->Settings->Updates->Free Add-ons, “Download Manager REST API” is listed as version 1.2.0 and with the status “Updated”
I can also find it under wp-admin->Downloads->Add-Ons (also 1.2.0)

We also tried to manually update wpdm. It was 5.0.5 and would not update to 5.0.8 through WordPress. To do so, our main technician said he had to “manually download 5.0.5, rename and deactivate the existing 5.0.5 version, upload 5.0.8 and re-validate the license”.

Considering the conflicting statuses of the version and the fact that we have not been able to update to the newest versions of the REST API nor WPDM through WordPress, could there perhaps be an issue with our installation that causes all these problems?

Apr 30, 2020 at 10:32 am in reply to: After upgrading to WP 5.4 /wp-json/wpdm/v1/packages gives 404 #127212

B
Participant

Weird, we definitely had it installed. However, we noticed that it was stuck on version 1.1, with the status “updated”. After manually upgrading to 1.2 we still get the same error. Could you take a look again?

Apr 30, 2020 at 6:38 am in reply to: After upgrading to WP 5.4 /wp-json/wpdm/v1/packages gives 404 #127190

B
Participant

Sorry about that, it should work now ๐Ÿ™‚

Apr 29, 2020 at 8:35 am in reply to: After upgrading to WP 5.4 /wp-json/wpdm/v1/packages gives 404 #127134

B
Participant

Any progress?

Its not my intention to stress you out, but without feedback, I cannot know if you have forgotten it or not. Additionally, by continuously asking for updates, I can better convey just how important this issue is for us.

Thanks

Apr 27, 2020 at 7:36 am in reply to: After upgrading to WP 5.4 /wp-json/wpdm/v1/packages gives 404 #126998

B
Participant

Hello,

As far as I know, I have not gotten any feedback since you said you were checking our setup. Have you had time to do so yet?

The ability to upload/update packages through the API is the main reason we chose this addon, so any feedback on whether or not you know why our API requests suddenly are denied would be highly appreciated.

Apr 22, 2020 at 2:14 pm in reply to: After upgrading to WP 5.4 /wp-json/wpdm/v1/packages gives 404 #126449

B
Participant

The last reply is marked as private and not visible for me. I assume it was sent to the thread’s original creator or an internal message between moderators, or was it meant for me?

Apr 22, 2020 at 7:47 am in reply to: After upgrading to WP 5.4 /wp-json/wpdm/v1/packages gives 404 #126431

B
Participant

Hi, did you find anything out of the ordinary?

The API simplified part of our operations quite significantly, so it is very important for us to get it back up again as soon as possible

Apr 20, 2020 at 12:59 pm in reply to: After upgrading to WP 5.4 /wp-json/wpdm/v1/packages gives 404 #126302

B
Participant
This reply has been marked as private.
Apr 20, 2020 at 12:57 pm in reply to: After upgrading to WP 5.4 /wp-json/wpdm/v1/packages gives 404 #126301

B
Participant

Hi, we are experiencing something similar. The requests that worked fine a couple of weeks ago now returns “404 no route was found matching the url”, which I suspect was caused by the upgrade of WP. Were you able identify the issue?

I’ll add wp-admin login details in a private reply below in case you want check our setup

Dec 13, 2019 at 9:45 am in reply to: Download list not respecting fixed theme #116691

B
Participant

I also see that is only related when the title is without spaces, i.e. LONG_TITLE_NAME instead of LONG TITLE NAME. Not a very important issue after all, however it will damage the GUI when these titles occur

Dec 13, 2019 at 9:42 am in reply to: Download list not respecting fixed theme #116690

B
Participant
This reply has been marked as private.
Dec 13, 2019 at 9:41 am in reply to: Download list not respecting fixed theme #116689

B
Participant

It is a private site with user login.. Let me know if is necessary still, as I would have to create user and mimic data (as the data available is copyrighted). I see that the issue occurs when the title of the package is too long. Could there be a way to automatically limit the title in some way..?

Oct 17, 2019 at 9:17 am in reply to: Creating packages through API and uploading files #113601

B
Participant
This reply has been marked as private.
Viewing 17 posts - 26 through 42 (of 42 total)
1 2