I've downloaded and deployed the sample-1.4.45.war of hawtio in jetty_9.2.x server with pullOnStartup flag as true. I can see dashbaord json files at .hawtio folder downloaded at home.user directory. The Dashboard tab is NOT appearing, however I get to see ActiveMQ, Camel, Wiki tabs.
I hope dashboard plugin is not missed in the downloaded war. The preferences does not show Dashboard plugin as well.
EDIT 1:
The Dashboard tab appears when I deployed sample-1.4.37.war.
Related
Using Liferay 7.3.5, i am consistently running into issues regarding theme deploy.
I am trying to upload a theme to my server using the instructions given in the following guide:
https://learn.liferay.com/dxp/latest/en/system-administration/installing-and-managing-apps/installing-apps.html
When i try uploading apps via the file system and into the deploy folder, the file appears to vanish and nothing happens. I have since been uploading it directly to the WAR folder, but i am now running into some issues when a theme is deployed that way.
I expect the theme to be uploaded and working properly, the CSS to be applied to the page(s) and the liferay menu to be intact.
Uploading the theme appears to go well and the theme shows inside the list you can choose from. Inside the list however, the theme doesn’t display a thumbnail.
Problems started once i uploaded multiple themes to the same liferay server.
On the site pages, the CSS is not properly applied and looks broken as if there isn’t any theme applied. The edit page button on the top right is invisible, as are the rest of the menu items.
Publishing the site or reselecting the theme do not resolve the issues, nor did a redeploy of the theme.
Does anybody know how to correctly upload a WAR file to the file system in Liferay 7.3.5, or am i overlooking something else?
UPDATE 22/09/2022
so i have narrowed down the issue a bit. When i first upload a theme to my war folder is works fine. However when deploying a another theme, the first one breaks.
I doesn't really matter which of the theme's i use as it seems to do it for all of them, I created a github with two simple theme war files. If you want to reproduce the issue.
https://github.com/Lincolnmyth/theme
All you have to do is follow the normal steps and upload the theme. Turn the server on, and check if it works. Then turn it back off again to add another one. You'll then start seeing issues in the first theme.
Such as liferay buttons changing the same colour as the background and the css from the theme not working. So for example, the januari theme should change the navbar and add a picture about it. If you upload the other theme however this doesn't work anymore.
I hope this works as a reproducible example
I have a local instance of Acumatica 2018 R2 that I am using for development and when I try to edit a Customization Project it is not pulling in the specific project and ID.
Local instance of the Custom Project editor
Where it says "Project" in the top left, it should say "Test5".
Here is how the editor should look:
Production Instance Custom Project Editor
I believe that I've configured my IIS setting correctly but I can't get it to perform correctly.
I've seen that happen before. It appears to be an Ajax glitch. When the customization project editor opens it displays Project as a placeholder first. Then an Ajax call fetch the proper project name to replace the template placeholder text.
There isn't much to do to resolve this issue. I suggest using a different web browser (Chrome seems to handle Ajax more reliably) and possibly issuing an IISReset command on the web server or if you don't have access to server a restart application from the apply updates page.
I’m experiencing an issue with customization projects in Acumatica 2017 R2 Build 17.203.0029.
Specifically, custom screens, while in my project XML, are not visible within the customization project browser nor can they be navigated to once published (which occurs without error). This only occurs on my staging server. Everything works fine in my local dev environment and even on a different instance of Acumatica. My local dev environment matches the staging server in every possible way (Acumatica version, other packages, etc.)
Older versions of the same customization project have been published before and did not exhibit this behavior. It’s only after I replaced the project with newer version of the same project that I encounter the missing custom screen issue.
As shown in the screenshot below, remnants of the custom screens are present in the Customized Screens window. And the ASPX files are present and shown in the Custom Files window.
Screenshot of missing custom screen data
When I compare the “Edit Project Items” objects between the staging the server and my local dev version, they appear the same.
It it possible that the internal customization or sitemap tables on the staging server have inconsistent data? Is there anyway to rebuild them?
The solution appears related to the users roles config. I had not assigned access rights to the custom forms. Doing so solved the issue. The custom screens are now accessible by direct URL and are shown in the customization project browser. Maybe this will help someone else.
I had this same issue when trying to Deploy the customization to another instance.
To fix it I had to go to the site manager and change the URL of the new page
from: "/Pages/SO/CustomName"
to: "~/Pages/SO/CustomName"
According to this page, "right-click the project and select Publish (or Publish Web Site for web site projects) to open the Publish Web wizard". What then comes up looks nothing like what is shown on that page, instead I get this:
which looks nothing like the "Publish Web wizard" described on the MS page. I have tried many of the options on that page, none of them lead to asking me to import my host's "publish profile".
Is there another way I can get to the Publish Web wizard so I can import my host's "publish profile"?
Try install this update: http://msdn.microsoft.com/library/jj161045
I had the same problem. This worked for me.
AFAIK, the Publish Web wizard (just like the one that is shown in the link you provided) is only available for Web application projects, not for Web Site projects, whereas the screenshot in your original question is the tool provided in Visual Studio to publish web sites.
In my case, I found it useful to convert the web site project to a web application project following the suggestions given here and explained in detail at the LearnAsp4.com site.
Hope it helps someone :).
Hi download upgrade 5 for VS 2012 from Microsoft site and install the executable. Then VS 2012 will display the publish wizard as shown for web application.
I had an existing publish profile under App_Data that had an invalid path in the pubxml, deleting that or fixing the path fixed it for me. I found this by going to "View > Other Windows > Web Publish Activity" then either select existing or try to create a new profile from the dropdown. This then gave me an error message which "Build > Publish Web App" didn't.
I recently upgraded from EE 1.6.6 -> 2.2.0.
After the upgrade one of my co-workers that is permissioned as an “Editor” on the site said that she can not longer find the place in the control panel to upload photo files.
I logged in as her and confirmed that the file upload feature is not exposed to her view.
I then logged in as admin and confirmed that “Editors” are allow to upload files (at the botton of the File Upload Permissions page) http://expressionengine.com/legacy_docs/cp/admin/weblog_administration/file_upload_preferences.html
It definitely says that “yes” Editors can upload files….
What am I missing? Is there something else I need to enable? Some config that might have been lost in my 2.2.0 upgrade?
You have probably sorted this by now but if she cannot see the file manager link at all, check that the member group has permission to access this via member groups > edit group > control panel access > can access content: file manager.
Are you referring to the "Upload File" link, which was previous in a green box under the "Submit Entry" button?
If so, this feature is now exposed through a small icon that is optionally enabled per field: