My Requirement is like Build in a process to lock a component during content development or updation.
For example, Vivek can still publish a page with OLT update while another author is updating another component in the same page. The previous version (that is not being updated) will be published along with vivek’s updates.
Since the User group is large & we have frequent updates we can't go for Pagelevel lock(multiple user will be working on the same Page).is der any Possible way to achieve this?... i hav tried the "FieldEditlockMode" but not works for me,am using AEM 6.1
Thanks
AEM Launches may satisfy your requirements, allowing your authors to edit components for future production releases without affecting an immediate release. Here is the documentation for 6.1:
Launches
Creating Launches
Editing Launches
Promoting Launches
Related
What is the best way to get auto-reloading to work when developing my website (my website runs on Mojolicious)?
There exists a development server called morbo, and it does update what is served automatically whenever I save changes to a source file, but the website itself does not reload automatically. I must manually refresh the page to see the changes.
What is a sane way to get this behavior? I am okay with using an additional tool if necessary.
My understanding is that Mojolicious::Plugin::AutoReload can do what you want by defining a auto_reload endpoint and having the UI poll your web app to check if the UI should reload.
The module was featured on the Mojolicious blog in 2018.
When we publish a page again we need to activate content in tools. I just need difference and use case. What is difference between activating content/page and publishing a page in AEM?
From Adobe Docs -
Certain terms related to publishing can be confused:
Publish / Unpublish These are the primary terms for the actions that
make your content publicly available on your publish environment (or
not).
Activate / Deactivate These terms are synonymous with
publish/unpublish.
Replicate / Replication These are the technical terms describing the
movement of data (e.g. page content, files, code, user comments) from
one environment to another such as when publishing or
reverse-replicating user comments.
Activate/Deactivate were the terminologies used in classic UI, you can see this on any version of AEM if you invoke the old screens - go to http://localhost:4502/siteadmin or use cf# to edit the page (http://localhost:4502/cf#/content/app/en.html) and go to page properties in side kick, you'll notice Activate/Deactivate.
On Touch UI, you'll notice Publish/unpublish, check page properties using the editor.html(http://localhost:4502/editor.html/content/app/en.html) or any other console in Touch UI.
They both mean the same - moving data from author environment to publish environment. Taking it a step further, it can also mean moving data from author to the dispatcher(via the publisher), with an added flexibility of clearing cache for that page during publishing/activating.
I have an existing fitness site ( showing exercises on different pieces of equipment) with menus available depending on whether the user is logged in.
Not sure of the best way of doing this but I would like to access the site via a touchscreen kiosk which will show a different welcome page and menus.
I know it can be done as a clone site which would mean copying all the execise data but is there a way for typo3 to recognise the type of device, assign it as a certain user and allow user level control of the content shown?
Regards
Paul
Device detecting is very complicated and TS conditions that should work were removed from TYPO3 core some time ago.
If it is important (and possible) to detect one kind of device you may create your own TS condition (userfunc).
But maybe another option would solve your problem:
Configure another page type which gets your modified layout for the start page.
Then you only needs to make sure the inital page is called with that specific page type.
An automatic login will be complicated. maybe it would be possible to use a permanent login, where a session cookie without endtime is stored.
If you're using TYPO3 version 8.7, you could use the extension aoe_ipauth (https://extensions.typo3.org/extension/aoe_ipauth/) to automatically log in a user based on IP address. There are several other extensions that do this, but I think most of the others are old and don't work in 8.7. There don't seem to be any that support TYPO3 9.5 yet.
I am facing a TYPO3 performance problem.
When I clear the cache of my website, the website waits for a user to visit pages again to cache the website. This seems to be a time consuming task and obviously this affects the performance.
So I would like to create a new extension or scheduler task which will check on a regular interval for pages which are not cached, and I want to force the pages to get cached.
So my question is: how is this possible?
There is an EXT:crawler, which allow you to index your website, including custom URLs with extnesion's parameters.
Current TER version is not compatible with TYPO3 6.2 yet, but latest git version is, so you can take it.
I am using the Magento ver. 1.4.0.1 Community Edition. The problem I am running into is that Magento only allows me to preview pages that I have already saved. This works fine if I am creating a new page - but what if I am editing a current page? I want to be sure that the changes I make look good on the site before saving them.
Does anyone know of a way to preview a static cms page before saving the changes made? I'm open to using some sort of plugin if anyone knows of one.
Thanks
Currently there isn't one in Magento, you'll just have to save it and view it.
A lot of the work I've done in Magento has been done on a development server, once everything was set it got moved to the production server. I'm not saying you need two servers, but having at least a development instance of Magento will help when editing a live site.
for non-trivial changes, I normally create a new page with a URL that's not linked anywhere and then load that up to preview, before copying the content/settings to the real page.