How to delete Topic 0 in a Moodle Course - moodle

So we are running a Moodle 3.7 system. Is it not possible to delete the Topic 0 section?
The gear icon doesnt show the delete option like it does for other sections. I have searched in the forums, before posting and came across this tracker issue: https://tracker.moodle.org/browse/MDL-60241?attachmentViewMode=list
Here they manually chnange the visibility in the database. This doesnt work for me. SInce students can still view the section.
Please help

It is impossible to delete section 0 in moodle if you're using the topics format. In fact even i you somehow managed to delete section 0 in the database the topic format code would catch this and reinsert section 0

Related

Magento 2 emptying CMS page table?

This is a very peculiar problem. A client's Magento 2.2.6 EE has emptied its cms page table twice today (sometime between 5pm EST and 5:20pm and again between 11:00pm and 11:30pm). I have disabled magento's crontab until a solution presents itself. The action log also has no records of access.
I combed through the action logs but nothing there stood out.
Has anyone come across this before? And how would I debug this? The system is setup to make hourly db snapshots so it's just a headache at this point.
Way interesting. I would start logging your db calls to find when and how the tables are emptied.
Check out this StackOverflow answer using MySQL.
If you get the exact query and user info, if Magento system user, search your whole install for that query reference.
Another option, if you have Magento plugins, disable all and see if the issue presents itself again.
Does the index reset when the table is emptied? If so, try disable truncate permissions from the Magento user and see what error is thrown when this action is attempted again. This would be a way to find the source of the call using the Magento error log.

Sitecore content editor not always asks to update broken links

I have a problem regarding broken links in Sitecore.
Our tree is filled by a console application with data from an other, older cms through the Sitecore item API.
We have products that are linked to Categories with a multilist. When an editor deletes a category, sitecore should give a popup to handle the broken links. This he does in 1 of the 4 cases. In the other cases Sitecore does not give a popup and the category deleted still appears in the multilist as "Not in the selection list".
Is there something wrong with how we insert the items or is it just Sitecore not being able to handle large amounts of data in the linking story?
FYI: we have around 160 categories and more than 1200 products.
Thank you in advance.
#Marek Musielak 's comment did the trick. Rebuilding the Links Database is the best way to ensure no broken links.

Some doubts related to the backend users in Typo3 6.1.1

I am pretty new in Typo3 (I came from Joomla and WordPress) and reading the documentation I have some doubts related to the user manage the user in this CMS:
I am using Typo3 6.1.1 and reading here it seems to me that the user managment is quite different (maybe the documentation is related to an old version of the CMS?): http://docs.typo3.org/typo3cms/GettingStartedTutorial/EditAndCreatePagesAndContent/CreateUsersGroups/Index.html
In particular I am not understanding if in the 6.1.1 the backend user can ben divided in groups or if they simply are backend user because if I go into: ADMIN TOOLS ---> Backend User I can see the backend user but not the groups, why?
Tnx
Andrea
As you can see in mentioned doc, BE users can be divided by groups and easiest way for creating BE groups and next BE users is using WEB > List module.
Just using workflow showed at screen of this section you need to create records of both types (blue arrows) on the highest page (with id 0 - on screenshot it's called New TYPO3 site)
I'm not quite sure about the reason, but Backend User module doesn't allow to manage BE groups directly, however there's a tip (which is general for whole TYPO3) - you can create a BE group ad hoc - during the process of creating BE user by using additional icons in the form, take a look to screenshot below, the yellow pencil and black plus allows you to edit/create related records without canceling current edition.

No rights on page-module level

I encounter a strange error. On page-module level i´m not allowed to create new page elements. If i do the same via the list-module page-elements are created and i can edit them (even in the page-module).
Also, if i created a flexible content element - e.g. columns - (via the list module) i CAN create new elements in the flexible content element, even in page module.
New elements are always on TOP of the page, meaning the first entry, and i can´t drag and drop them. Well, i can, but changes do not come in effect. To sort the elements I have to edit the page properties, and sort content.
The user has every right(!) given by the user settings, and it is TYPO3 4.7.4
Does anyone know where i have to look for a solution? Thanks in advance!
Edit 1
This error appears in the log:
Attempt to insert record on page '[root-level]' (0) where this table, tt_content, is not allowed (msg#1.1.11)
Again: Creating Elements IS working via the List-Module.
This error is causen because the field t3ver_swapmode in the page table was removed since TYPO3 4.7 (Maybe in combination with TemplaVoila).
I dont know whats exactly going on here (didnt had the time to find that out), but the solution is of cource simple. I uploaded my fix to the TYPO repository under the key swapmodefix http://typo3.org/extensions/repository/view/swapmodefix
The extension appears in a couple of hours, good luck!
You need to select a page inside the pagetree first. You may not create content elements on the root page.
It might be that the selection is lost, but still visibel. Just click the page again.

Umbraco media section missing?

I'm admin, but I can't see the media node anymore, I can't see it in my user section, where I can give users access to sections?
ANyone had this problem before?
Fixed this, this can be caused by, the startMediaID in the DB being incorrectly set to -1 (somehow) change it to a node value.