Activities of "hinairusu"

Thank you for the update and clarification. It's strange that it's not a feature you plan to support, but it's nice to know that it's been acknowledged and that it is working as intended.

Okay, so I've got an update.

I've ran the restore that you askedm and got a lot of "info : NotFound" appearing. I accidently closed the window trying to grab a screenshit, so I ran it again and now I've got "Restored:" across the board.

I cannot however add a new module. List is still appearing empty, and only Admin.Application appears in the package manager.

Actually, as I've been typing this, I've noticed this occuring.

It's like it can get to the feed, and if I ask for a package explicitly, it lets me get it, but I can't search through packages, only list the top 1.

But if I change it to Nuget.Org

One thing I would like personally is a notice that the ticket investigation has started, or even has been seen, on a post.

I've seen one ticket today that's over 9 days old without even initial feedback on it, just a chaser by the OP.

I've logged a P1 ticket for us today as we can't do any work with the feed out, but no idea if it's even been seen by the support team.

Hi Team,

I've checked through and it doesn't seem like anyone has reported this yet. My Nuget feed is only returning the first entry on the list, giving me no options to continue developing, or restore any project.

Any idea if it's something I need to update my side, or if it's not when it will be avaliable again?

Nevermind, I think I have figured it out. Thank you.

It's frustrating I cant use the upload modal component out of the box, as I love the way it looks/feels, but at least now I have something to be working with.

i have the directory section working, I have the file pull down and display.

The upload however I still have issues with. the IFileDescriptorAppService doesn't have any methods for the PreUploadInfo, just a create with stream. I could swap it out for a direct rest call, but that seems counter to the ABP design, and if I did I don't understand the interaction between PreUploadInfo and Upload. Is the pre info required?

I have set up a new project on MVc, And I can see the API calls being sent. I think I have a rough ida of how to use these now. I've maaged to get the directory contents out as a DirectoryContentDto.

Is there any way to display the file in question (Assume for the moment that it's a JPG) in the browser? so far everything I have tried just downloads the file, rather than displaying it in the browser.

I'm looking to list the files in the directory as cards, in <img> tags.

I see that most of the comments are abstract.
To fine-tune our documentation and get started steps, we need concrete examples.
Because for me it's very straightforward to kick-start a project.
Imagine that you start a new scratch ASP.NET Core project with Docker, DevExpress, and Identity Server with a tiered architecture, would it be slaphappy?

As a developer in this exact situation, I have a concrete example for you. The File Management Module Documentation does not explain how to install it correctly.

https://docs.abp.io/en/commercial/latest/modules/file-management

There is no mention in here of having to insert the correct connection string (FileManagement), the adjustments to EntityFrameworkCoreModule.cs, the ocelot additions which have to be made as it inserts under FileManagement instead of the module you install it into, and if you install it via Suite having to change the UI if you're on BlazorServer as it loads the wrong one. If I am following a set of installation instructions, I would expect at the end of the instructions to be able to hand it to a test user. It may not be production ready, but it should at least work.

Update: The Doc actually says about the connection string now. May have missed it, or may be a recent edit: "This module uses FileManagement for the connection string name. If you don't define a connection string with this name, it fallbacks to the Default connection string." << But it most definitely does not fall back to the default connection string.

I have no doubt that with access to the source code it would have been clearer to pick up, but as it stands it was incredibly frustrating having to reach out to support after over a week of trying to resolve it ourselves and use up one of the few tickets we have.

I have no doubt that now we have one successful module installed, it'll be more obvious as to what to do for the next one (Looking at Payments next, so hoping it's a similar install process) but i wouldn't describe it as "very straightforward to kick-start a project." Maybe if you was looking for a basic MVC webpage, yes. but the rest of the features? Not really.

The bot automatically closes it, if there's no activity from the ticket owner. @kirotech, I reopened the ticket. and please send an email to info@abp.io if you have such issues. Many people are subscribed to this topic and reading your -personal- problem.

Hey I don't think this problem just for us. I would suggest you to keep tickets open for at least 30 days. Because not everybody has time to respond with technical details in 7 days.

Another suggestion I would like to make. We need private tickets. Because paying customers are paying for support also why all tickets has to be public? Some problems are delicate and includes security questions like we have with your not working oauth openid functionality we have to share our applications configurations publicly this just doesn't make any sense.

Also another thing. I think your support tickets creator filter is privacy problem. If I search @gmail.com I can find emails from your support system database. Also I can find your customers account names. I would suggest to improve that or just remove it from public.

Also another thing how you can improve you support is by providing reliable information when you going to release bug fixes what we found in your abp commercial. As example your abp commercial payments bugs which we reported and had to ask several times which version fix will be included in.

To ask questions privately, you can upgrade to the Enterprise License plan.

I understand your concern about email privacy but that combo box you mention only shows usernames. If the account owner writes his email to the username area then it'll be shown, if he writes his cell phone its shown. if we remove it from there, it's still visible in the question-answer sections. hence this is not a privacy deal.

On the other hand, if you want to see raw and detailed change logs for every release, please check the full change logs document that we recently started to publish https://docs.abp.io/en/commercial/7.1/change-logs/index

We have to pay 10000 for license to get private tickets? Doesn't look like fair offer sorry. Really appreciate your offer, but no thank you

If your user name combo box is fine with you it is 100% fine with me. No worries here. From customer perspective it just looks strange when I search and I find your customers emails and phones. but if there is no problem it is no problem.

I'm not looking for change logs I'm looking for reliable information provided in tickets when bug fix reported going to be released. Do you see the difference?

To further expand on this point.

One response we got from support was

I suggest you consider upgrading your license to get the source code of the modules.: )

Which I understand is very tongue in cheek, and got a chuckle out of me after I'd calmed down a little, but is incredibly frustrating when you are starting out with your product and paid for the ccommercial modules to "jump-start your project" suddenly appears to be not a 1.5/3k investment but a 6/10K?

I imagine the sentiment is the same when it comes to tickets. It appears you're getting what you want, but in reality, not so much.

It's also worth highlighting that your change logs do not include all the changes made at the "ull change logs document". Having to go hunting through GItHub PRs for changes is not okay. An example of this being the recent resolution to authentication tokens expiration and the new override methond (Which is amazing, thank you.)

This is the Microservices Template set up from V7 and upgraded as updates have been released. I've not added any extra references to this module, I don't think I've actually changed anything in it actually.

I assumed they have to be the same, I've manually updated it so that my solution functions again. None of the other solutions threw this error on updating, they all updated across the board, just this SaaS module which doesn't.

Thank you very much. Adding in options.IntrospectAccessToken(); appears to have resolved it, although I'll need to confirm it in the morning when my current token expires :)