Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Personabar is missing after installing dnnsharp AF #3549

Closed
schotman opened this issue Feb 7, 2020 · 5 comments
Closed

Personabar is missing after installing dnnsharp AF #3549

schotman opened this issue Feb 7, 2020 · 5 comments

Comments

@schotman
Copy link
Contributor

schotman commented Feb 7, 2020

Description of bug

Provide a clear and concise description of the bug.

Steps to reproduce

List the precise steps to reproduce the bug:

  1. start with a dnn804 install
  2. upgraded to dnn950rc1
  3. looks fine, can add content, install open content module, add pages: No problems
  4. install AF DnnSharp.ActionForm-05.01.03-Install.Hotfixes.

After this installation the personabar was no longer visible with the following errors: 

image

Affected version

  • [X ] 9.5.0 rc1 build

Affected browser

  • [x ] Chrome
@bdukes
Copy link
Contributor

bdukes commented Feb 7, 2020

@bogdan-litescu @dimarobert Do you have a version of Action Form available that @schotman can test on the DNN 9.5.0 RC1? Or, @dimarobert, does #3544 need to land before DNN Sharp modules can work?

@schotman
Copy link
Contributor Author

schotman commented Feb 19, 2020

Tested an internal build of AF against the nightly build of DNNplatform.
This worked, that is, some basic tested showed no problems with the module (apart from a package install error, IIS, see screenshot).
The nightly build contains the pull request from @dimarobert which made it work I suppose.

Not sure if this IIS error is a special case for AF, I did not see it when installing OpenContent.

image

@sleupold
Copy link
Contributor

@schotman
DNN 9.5.0 has been released yesterday, please test against this version.

@stale
Copy link

stale bot commented May 19, 2020

We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically.
If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!

@stale stale bot added the stale label May 19, 2020
@schotman
Copy link
Contributor Author

solved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants