Is there any way that i can do it for whole site?
For individual user instance, Go to user account settings > Preferences > Author mode, select classicUI
more info here: https://docs.adobe.com/docs/en/aem/6-3/author/author-environment/user-properties.html#Account Settings
Alternatively, to have all users of an AEM instance use the Classic UI by default, start off by going to the AEM Web Console Configuration (/system/console/configMgr). Make sure you’re signed in as an admin and do a find for “WCM Authoring UI Mode Service.” If the service is not visible, click on the OSGi button at the top followed by Configuration, and then do another find. Click on “WCM Authoring UI Mode Service” and change the “Default authoring UI mode” to “CLASSIC” (or back again to “TOUCH,” depending on what you want to do). You must enter “CLASSIC” or “TOUCH” in uppercase letters or an error message will show up when opening a site. Changing this setting will make the chosen UI the default for all sites of the AEM instance. When opening a site with /siteadmin, or /sites.html/content, the site should now open using the Classic UI. This should be the case for all users.
Related
I am working with a site using the Microsoft Developer Program. I am able to use the new Change the look feature on modern Communication sites to adjust the theme.
I created a theme using Powershell
I created a Communicators site and selected the Custom theme and used a PowerShell cmdlet to set that site as the homepage. I am still able to change the theme on that site by going to Settings > Change the look > Theme. The default and custom theme appear in the menu to select.
I attempted to follow the instructions on creating a Site Design to test out the feature of potentially exploring site designs. I ran into some issues of the feature I was attempting to use was not supported yet. I did not create any site designs. I use the Get_SPOSiteDesign cmdlet and nothing is returned.
I then created another communications site. I was just going to build these one at a time since Site designs did not meet my goal. I wanted to change the theme to the Custom theme, I go to Settings > Change the look > Theme and it closes the Change the look menu in the panel and returns me to the Settings panel.
I am able to go to Settings > Change the look > Header, Navigation and Footer successfully. Only the Theme option causes this error. I am unable to change the theme.
I used a PowerShell cmdlet to ensure the themes were not hidden, Set-SPOHideDefaultThemes $false. This is set.
I then created a second, third a fourth Communications site (using the Topic, Showcase and Blank designs) and the same error above occurs not being able to access the theme menu.
I then created a Team site. I am able to access the Theme and change to the Custom theme or one of the default selections.
I need help as to why new Communication sites I create in my environment will not allow me to access the theme menu, but homesites and team site do allow this. What do I need to do to correct this?
I too am coming across the same issue. I have attempted it in difference browsers and in incognito to verify it wasn't an extension or browser specific issue. Have you discovered a resolution or opened a ticket yet?
We have the same issue on our tenant and have opened a ticket a MS support. They confirmed that this a bug and are going to solve it.
For now we have a workaround via PNP Powershell.
When you set the theme first via Set-PnPWebTheme -Theme "Custom Theme", the option to modify the theme via the browser works again.
I would like to add functionality to the AtTask system by "adding a layer".
What I want to know is whether this can be achieved with a plug-in for Internet Explorer.
To give a concrete example:
This extra layer would allow users to click on "Online Edit" document (which is not available right now). The linked application will open, and when you click save, the file is loaded back to AtTask.
All this happens in the background via the AtTask API, and is transparent to the user.
The question is: is it possible to add functionality to a site by somehow adding layers?
Last comment: this plug-in (or whatever needs to be installed inbto the browser) will only be visible/active when accesing the AtTask website.
Thanks in advance for your responses.
Within the confines of AtTask your best bet is to use an "External Page" create a service that handles the data in the manner you need.
The Dashboard that contains your External Page can be added as a tab via Layout Templates.
Most of the heavy lifting would have to be handled by your application. You would have to link the document(s) you wish to edit.
Some sort of referrer would be necessary to place the revised document back into AtTask. The method in which the client can do this would be determined by your preference and requirements. I am sure you can find some sort of Wiz-Bang jQuery uploader.
Depending on the level of control you have with your user base, you could make an Application URL
Windows : Registering an Application to a URI Scheme
OS X : Launching Scripts from Webpage Links
I do not know of any other way to handle this other than what Steve suggested.
Having said that a possible solution to this is to create a new application and iframe in AtTask.
At the top or wherever on the page your application could have a link for "Online Edit". Then you would use javascript to extract the task id, project id or any other needed information you need for the api to get the needed content to edit. Then save using the same api information.
I have not tried this type of method but theoretically it could work.
In basic search form I have included checkboxes to detect duplicates on name & phone number.
How shall i proceed further.I have included fields on /custom/modules/Contacts/metadata/SearchFields.php and searchdefs.php.
Please help.
SugarCRM's Basic and Advanced Search field arrnagements can (and should) be configured using the Studio Tool. Log in as a System Administrator, click the Admin link in the top right corner and find the link for Studio
Within Studio, navigate to the module you're like to configure, go into Layouts, then Search, then Basic Search. The screen arrangement can be configured using drag-and-drop 'bricks' to represent the fields. All database fields for the module can be added to the Basic or Advanced search filters.
The screen can be configured using code, but I don't see why you would opt to do that. If you do, though, be sure to clear your cache using Repair and Rebuild or by enabling Developer Mode in the System Settings.
I have developed a front-end system plugin for Joomla 3.0 which replaces keywords for HTML formatted objects. This works perfectly in my local lab environment but when installed on the hosted site (WHM/cPanel) it causes issues with the administration area and prevents the administrators from editing the articles.
When the administrator clicks on a article to edit the page attempts to load then appears to go back to the same page. I have developed this as a front-end plugin only so I shouldn't affect the administration area.
The problem is also preventing admin from creating anything new (news, blogs, content, menu items etc.)
As this does not happen within my lab I can only assume the issue is with some server settings which I may need to enable/disable. I have complete administrative access to both WHM, cPanel and Joomla so can change settings where ever needed...
Things I have observed:
The article URL changes from:
/administrator/index.php?option=com_content&view=article&layout=edit&id=7
to:
/administrator/index.php?option=com_content&view=article&layout=edit&id=7
when the plugin is enabled. Notice the ampersand has changed to amp;. This makes me think it could be something to do with UTF-8 character encoding has been set in MySQL to utf8general_ci.
Any pointers on configurations I may need to change would be greatly received.
Question: How do I prevent this from occurring (without removing my essential plugin).
If you create System Plugin that should work only on front-end you have to check in your plugin if current page is front-end. You can do it using this function: JFactory::getApplication()->isSite() or JFactory::getApplication()->isAdmin()
Example usage (I assume you use onAfterRender event):
function onAfterRender() {
// Exit if current page is from Administration panel
if( JFactory::getApplication()->isAdmin() ) return;
/* your plugin main code goes here*/
}
It will prevent your plugin from modifying administration panel output. If you already done it and it does check like it should to, there is no way that reason of your problems is that plugin.
I have installed both author and publish instances of CQ5.5 on my PC. But when I add a new page and publish it, it does not appear in the publish instance. Only a blank page is rendered.
I have tried activating it both from the siteadmin and from the Replication page in Tools. Only the navigation item appears in the Publish instance.
I checked the Request logs also. But it only gives a
200 response(OK)
Can someone please help me on this ?
You need to activate/replicate your /apps/site folder where all of your templates and components are located to push it from your author instance to your publish instance. Activating a page doesn't automatically activate the components and templates it uses.
Go to:
http://localhost:4502/etc/replication/treeactivation.html
Browse to or type /apps/[your site] in the path field
Set the check boxes to fit what you want to activate (Unchecking all will make everything under the selected path activate)
Click 'Dry Run' to see what will get activated without actually activating. (This is more of an informative step to help ensure you don't activate something not intended in a production setting)
Click 'Activate' to activate.
You can then check your publish instance to see your templates and code are there.
It is easy to miss activating your apps folder as there is no ui like the website admin for pages where you can activate.
Activating a page/folder/asset does not activate sub-pages/folders/assets. This can cause confusion especially when working with folders.
Generally if you need to activate a tree the best way is to use the tree activation utility
The only time I've ever seen this is when the code is not installed. That would be the first thing that I'd check. Go to (assuming you have your publisher on port 4503)
http://localhost:4503/crx/de
You should have your the code in /apps and you should be able to find the content page in /content too.
The reason this happens is that the sling:resourceType property points to a component that doesn't exist so it uses the default which is an empty output.
You have to build the code to both the environments (author as well as publish). This way both the environments will have the same copy of source code installed in the form of cq5 packages and felix bundles. Then if you create a new page or drop any component on any existing page, it will appear the same on publish environment after activating the same either through 'Activate Page' link in sidekick or through replication tree activation page.