Sitecore OPTIONS menu on Builder tab missing - sitecore

For some reason I no longer see the OPTIONS menu item when I am on the Builder tab for a template. I have not needed to access this tab for months so I am not aware of when it went missing. I am on Sitecore 8.2 (rev. 160729). I have not installed any new modules or packages recently so I do not think its related to that. Has anyone experienced this behavior?

Based on our comments, the only reason why the option tab is not appearing is because of the css styling display:none.
This is not caused by Sitecore css or js files but rather a custom implementation. I would suggest to check your css files or even JavaScript files.
It might also be the case that there was a development to hide or show certain tabs in the ribbon which in brief may be due to custom development of ribbons or even commands. So, you may check the different commands or ribbons implemented.
Finally, which I think may be of least importance, is the development of SPEAK UI. It might be that you have a 3rd party module which is injecting the styling or a module implemented.

Related

How do I disable autocomplete in Apex Oracle 20.2?

I am learning SQL and the Udemy course I'm following has us using apex.oracle.com a lot. That site recently updated to version 20.2. Their "New Features" page contains the following:
A new code editor has been implemented throughout the development environment, resulting in a greatly improved code editing experience. The improved editor includes enhanced code completion, syntax highlighting and vastly improved accessibility.
This is a LIE. The code editor now constantly tries to suggest things as I'm typing. This is extremely irritating and I can't find a way to disable it. How do I turn off this undesired flashy distracting spam?
Assistance would be greatly appreciated.
This is a LIE
I wholeheartedly disagree with you, and I would also ask of you to be more civil. The new editor contains many enhancements that benefit professional APEX developers, who don't only use it as a SQL playground.
With that being said, I agree that the word-based-suggestions for SQL can be annoying at times. For example, they appear in SQL Commands, but not in Page Designer on pages with implicit suggestions such as page items. I would actually consider this to be a bug.
For APEX 21.1, I would expect there to be many more editor options exposed. For now, this is a workaround for you:
Download the FOS Browser Extension. A small feature of this extension is the injection of (for now) 2 extra editor settings in APEX 20.2 environments. One of them is to enable/disable suggestions completely. Keep in mind that this setting will be stored in local storage, and will be applied globally, so you also won't get page item suggestions in Page Designer.

Template with TYPO3 v10

I would like to do a project with TYPO3 v10 I'm new with this CMS and I need to create different templates for different pages but I don't understand which code I need to change.
I already install a sitepackage from this site https://www.sitepackagebuilder.com/
It work well but I need to create my own templates and I want to edit the content of my templates in the back end administration like in the picture.
I hope I'm clear
thanks for help :)
I am not sure if there is a misconception in the question or if I have interpreted incorrectly. In any case, I hope this helps:
It is important to differentiate between content + template in TYPO3:
content
In the screenshot posted in the question, you see the TYPO3 backend, which is a view for editing content, administration etc. There you see the page module is opened in the left column (1), you see the page tree in the middle column (2) and the page layout for editing content on the selected page in the right column (3). Here, you can insert and edit the content, that will be displayed on a page.
Template
In TYPO3, the template is what makes up the automatically generated parts of the page such as header, footer, menu, breadcrumb etc.
It work well but I need to create my own templates and I want to edit the content of my templates in the back end administration like in the picture.
Editing the template in the backend with a Wysiwyg ("what you see is what you get") editor, similarly to editing the content is not really possible in TYPO3 AFAIK - at least not out of the box. For this, you would need a template builder. The only thing I have seen so far that comes close to this is toujou (I am not affiliated with them, just wanted to mention it). They have something which you could call a website builder. But AFAIK, you can't download it, they provide this as a service.
The sitepackage builder - as far as I know - pretty much just creates a sitepackage based on the bootstrap package extension which you would have to further modify by editing the files.
What you can also do is edit the TypoScript in the backend. Just go to the "Template" module in the left column. But, this made more sense in the past, because a lot more was done with TypoScript. Nowadays, you usually use a combination of Fluid and TypoScript and you can't edit the Fluid files in the backend.
While in the past, a lot more was done in the backend or could be done in the backend, everything is moving towards maintaining changes in files and extensions, where the template is maintained in a sitepackage. For some things both is still possible (backend and extension), e.g. backend layouts, TypoScript etc.
Moving the configuration + templates from the backend (and storing them in the database or as files) to a dedicated extension has several advantages:
Every configuration etc. is bundled into one extension, this makes it easier to install in another site, on a testsystem, exchange it etc.
the sitepackage can be put in a version control system (e.g. git) which has a bunch of other advantages such as easy rollback to a previous version, referencing issues etc.
The downside is that you need more technical expertise and there is a learning curve.
see also:
The Anatomy of Sitepackages
Sitepackage Tutorial
I understand that it might be pretty cool to assemble a template in the backend - just like you can do with the content. Maybe someone else knows how to do that with TYPO3.
You can also check out these resources which seem to go in the direction of what you are looking for:
TYPO3 extension mask (documentation)
T3terminal
in the official documentation you can find the structure of folders where the files for your layout are stored.
More details on fluid templating in this document
Now you want a possibility for editors to select between different page layouts. An often used way is to use the possibility to select different backend layouts and select a frontend layout accordingly.
This is shown in the video on this page or in the documents you can find if you uses the searches on that page.

ShowEditor and Rich Text Field is not displaying in sitecore 7.1 application

We have migrated an application from sitecore 6.2 to sitecore 7.1.
We are facing an issue related to Rich Text Field which is not showing up when I open a content item. The Show Editor is also not popping up the Rich Text Editor for editing.
When I am facing this kind of issues after upgrading I tend to put tickets # support.sitecore.net and dig some deeper into it myself. What I normally do is get a clean web.config + complete fresh bin folder of the Sitecore version I've upgraded to. Also I make sure that I grab the /sitecore folder with it.
Then I will compare the fresh bin with the solution bin and replace any assemblies that are not the same. From there I will also do a folder compare (using beyond compare or any other good compare tool) to make sure I got all the necessary files from there. Also I make sure that I look for any posts on the Sitecore forum containing the same problems. Don't forget to view your logs, as they will sometime help you find your problem quicker.

Upgrade from CMS 6.5 with shared source item buckets to CMS 7.0... how?

We are currently running Sitecore CMS 6.5 (120706) with the shared source Item Buckets module installed from here:
https://github.com/jerrong/Sitecore-Item-Buckets/tree/master/sitecorepackages/ItemBuckets%206.5%20NET_40/Final
We wish to upgrade to CMS version 7.0. I'm told that there is currently no upgrade path and to expect one in a few months. However we would prefer not to have to wait on this.
Item buckets is used only for a single section of our site. Everything else is delivered via the standard content tree.
We have tried upgrading to 6.6 first as required by the documented upgrade procedure, despite it mentioning later in the instructions that the shared source item buckets module is unfortunately unsupported for upgrade. Confirmed that this definitely does not work, we receive the error:
Exception Details: System.IO.FileLoadException: Could not load file or assembly 'Lucene.Net, Version=2.3.1.3, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
We also tried disabling Item Buckets by removing the .config files etc. but we had further problems, presumably because of the actual content/data template changes that were made by the Item Buckets update.
We are thinking of trying a clean install of CMS 7.0, and then migrating our custom code base, items in the content tree (including data templates, layouts, renderings, etc) with Sitecore packages to work around the issue.
Can someone validate this approach, or better still suggest a much less painful solution!?
Many Thanks
(this is not official Sitecore advice as that is still being worked on disclaimer,disclaimer!)
Some ideas that might help ..
First we need to work on the data side of things (forget front end code for a second)
You could Un-bucket your items so that they are again plain Sitecore items. You could then remove the item bucket module templates and fields as you mentioned before (by 'unbucketing' you should now have no reliance on the bucketing templates etc.)
You could also look at creating an 'anti-package' using Sitecore Rocks, either way this should give you a site closer to a site before the item buckets module.
You could then get a base/clean install of 6.5 (120706) and then compare it to your working copy 'master' database using a tool like Sitecore Courier.
Sitecore Courier - https://github.com/adoprog/Sitecore-Courier - Allows you to compare 2 versions of Sitecore DB against each other and make an update package of that difference.
This should make you an update package of all the changes that have been made to your 'master' database so that you can, in theory, install this into a fresh copy of Sitecore.
You could see how far this gets you when you install this update package, in theory then you can re-bucket your section that used the old buckets module but using the new built-in buckets.
Front-end code wise, the old item buckets modules way of accessing the search has been completely re-written as that it now uses Linq To Sitecore. Hopefully this will be easier to migrate and the buckets will still work in largely the same way (hopefully better hehe!)
Like Ruud I would be interested to hear about others techniques for doing this.
Any extra complexity could come from thing like :
1) How much customisation of the core database you have done
2) How many new field types and XAML applications you may have written
At this point, there is no good solution for this yet.
If you are actively using the module, there is no way to upgrade right now (not that I know of).
If you are not using the module at all, you can remove everything in Sitecore that has to do with ItemBuckets.
This is a manual job for now... (I've done this with success in a 6.5 environment).
To be sure you remove everything, open the item buckets installation package (the ZIP file) to see what items are installed and manually remove all those items from Sitecore (this will include templates, fields, field types, settings).
You can also use the search in the content editor to search for "itembucket" or "item bucket" and find related items that way.
Another way is to search with SQL directly in the master and core database.
Once you have removed everything in Sitecore and configuration that is related to the buckets, rebuild the link database and run a database cleanup (from control panel) and you should be good to go.
It's a dirty job...
If anyone has a better way, I'd love to hear about it!
the problem you are having there is that the item buckets code was compiled against Lucene.Net 2.9 and Sitecore 7 has v3.0.3.
You could add an assembley binding in in the web.config configuration/runtime section that maps the old version to the new and then fix any issues you get with deprecated methods etc...
You will probably also want to remove the Item Buckets module before the upgrade as suggested as the new bucket templates & items may conflict with the shared source versions. You would at least need to remove the Item buckets config and dll's from the bin folders as these could also conflict.
I don't think there is a simple way of doing it yet or Sitecore would have given out an upgrade path already.

How to get consolidated report of project mile stones for all projects in Redmine

We are Redmine as a Project management tool. It has been working great and we are happy with it. We now have a new requirement now. Our management wants to see a report showing each project's delivery date, manager, start date, total issues, open issues, closed issues. I searched at several places for quite some time and did not get a solution. I appreciate if someone can offer help.
This is, for me personally, the single thing JIRA is better at :)
Anyway, that being said, you can get a summary of all open versions on your "my page", eh, page, by using this plugin:
https://github.com/bradbeattie/redmine-my-widgets-plugin
And you can also add custom queries to "my page".
You can get much of what you want in the issue report. Click the Summary button in the sidebar of the issues page in each project. Example
Create one generic top level project. Calendar, gantt charts, issues, etc, for the top level project will show everything for every project that's nested underneath.
If you are properly adding roadmaps/milestones to all the projects, you can use My Roadmaps plugin to get a consolidated visibility:
http://www.redmine.org/plugins/my_roadmaps
It works fine with 1.2 and 1.4 versions.