last time I do some updated.
I uploaded to CRX installed and did replication.
On component A works ok (author & & publisher)
On component B on author works have new data, publisher have old data
What I saw is when I unpublished page with component B is still visible on publisher instance.
If you replicate a package that contains a deactivated page, that page will be still visible because AEM ignores the deactivated status on the publish instance, if the page exists it will be displayed. To avoid this:
Do not replicate deactivated pages via package.
And/or use the on/off property where a page won't be available even if it exists in the publish instance. See https://experienceleague.adobe.com/docs/experience-manager-64/classic-ui/authoring/classic-page-author-publish-pages.html?lang=en#scheduled-activation-deactivation-on-off-time
Related
I recently just got into Acumatica Report Designer. I have followed a quick tutorial I had found at https://www.timrodman.com/building-your-first-report-in-acumatica-report-designer/, but when I put my report into my Local instance of Acumatica I can not see it. I can directly put the screen id in the URL, but if I search it nothing pops up. I changed all the access rights to granted for the report itself. I have all admin rights on my local instance. What am I missing?
Make sure that you are adding a Workspace and category for anything with Modern UI
Note the top report will show up on Inventory Workspace under the Physical Inventory Category
The bottom 4 reports are loaded on the server but not mapped to the ui so can be accessed in code via an action etc. but are not on the ui. And would be under hidden for security purposes
Site Map Screen
Security View under hidden Workspace
Can you post a picture of your sitemap? My guess is that your URL is incorrect.
I noticed that from December 1 published extensions are not visible on the page https://chrome.google.com/webstore/ and google after such indexing is visible? Could it be some sort of algorithm update?
Or is it a temporary error?
You may want to try Updating a web app's Chrome Web Store listing with these steps:
Open the web app script in the script editor.
Click Publish > Register in Chrome Web Store. Click Edit store item. This will bring up the Edit Item form you filled out during publication.
Make the changes you want to the description, graphic assets or other settings.
Click Publish changes.
Visit the Chrome Web Store developer dashboard to see the publication status of your web app. Note that the publication process can take up to an hour to finish. Once the "Status" column says "Published", your web app will be available in the store.
In addition to that, you may also check the possible reasons why your item may not be showing in search.
If any of the given links doesn't help, I suggest that you submit your issue.
I used the Azure portal to install an instance of Umbraco.
I need to use the Umbraco forms for a simple contact form.
The Umbraco instance contains the forms and I can perfectly create and configure everything I need about forms (fields, workflows, ...).
Problem is that I can't get to have it on any page.
The video here shows how to do it but when I click on the button as shown 23 seconds in the video, I can't find the forms and therefore not add my forms.
I tried to add the Razor line that it seem to generate based on the guid I get on the Form configuration page but when I save, the online page (I mean, the page of the actual website) is crashing (Yellow asp.net error page).
Does anybody knows what is going on here?
EDIT: Maybe I should mention that I did click on the Install button in the Forms section and waited until it refreshed the page. Surprisingly, it continues to prompt for installation now.
I found the answer.
Seems like when we installed Umbraco at first on Azure, the auto install failed at taking the database into account.
We had to manually edit the config file to make sure everything was all right.
However, some bits for the Forms were not referenced properly.
So I uninstalled the forms completely and reinstalled them from scratch and it started to work fine.
I made a change to my v4 master at the application level to hide a certain piece of HTML code (the developer dashboard to be specific). I assumed I could edit it at the application level and then all site collections created within that application would inherit the changed v4 master and hide the element.
This is not the case though... in addition, I tried to edit the master in 14\TEMPLATES\LAYOUTS with no success either.
The only thing I have gotten to work is editing the v4 in SP designer at the site level (which is unaccepable to me as I want to provision a new site collection and not have to manually change this every time).
Any suggestions / known fixes for the issue I am encountering?
Try to hide what do you want thru style sheet CSS or don't update the default v4 mater page not recommended, create a new copy of V4 and do you updates then create Staplers features and on every site collection created change it's master page to the new one yo have created and for the old created site collection run thru code and activate the Staplee feature on each site collection to do the same.
I am trying to add a view to a custom list. The target is MOSS 2007, I am using VS2008 w/ VSeWSS 1.3. The feature already has a custom list definition, including a custom view called "Calendar". To get started I thought I'd create another view called NewCalendar that is simply a duplicate of the existing custom view Calendar.
So, I copied Calendar.aspx to NewCalendar.aspx, copied the existing "View" node for the current calendar and pasted a new node, then changed the following attributes of the new node: DisplayName, Url, and DefaultView.
When I refresh WSP View NewCalendar.aspx shows up. When I deploy and go to NewCalendar.aspx i get a 404. Using SharePoint Manager I confirm the page is not present.
How do I add a custom view via a feature so that it shows up in the "View" drop-down?
UPDATE: It works if I create a new instance of my custom list. How do I get the custom view to show up on existing lists?
Unfortunately features in general are not retroactive. You cannot update a feature and expect all existing items that were created from that feature to be updated. This i assume is by design. If this were possible it could potentially have far reaching (unexpected) consequences.
In these senario's i script out a retrofit script, when publishing the new feature.