Unknown category Moodle - moodle

Sometimes for any reason, the moodle shows the message unknown category and you can't do anything. Does somebody know how to fix this problem?

To fix this problem, I entered the database and deleted the last record on the table mdl_course, because it was the last action that I did. After this, I entered to moodle site normally. Don't forget to remember what was the last action you did.

Related

FirebaseFirestore document not deleted

I have a very anxious and bad experience since 02 days with my FiresFirebase Firestore.
Before this, everything was perfect, but since 02 days, I'm not able anymore to delete the document in my database.
I first noticed that the document was no longer erased by the application by the app process needed.
Then i tried directly to erase the document, i was very surprise. When i delete the doc, firstly the docs has been deleted, but after some times the same docs appear again.
I have looked the rules, evrything is fine as the google documentation recommanded, and the thing is, i worked with my app project like that before without any problem... but sudundly this one appear and i don't understant why.
Please, can you help me to fix this, I'm about to finalize this app, and before fix that ..... I can't do anything !!!!
PLEASE HELP ME ......

Unable to find component with id 'FooPopup'

I found this strange error in the production logs:
Unable to find component with id 'FooPopup' in [Form [Component id = FooForm]]
Expected: 'FooPanel:FooForm:FooPopup'.
Found with similar names: 'FooPanel:FooForm:FooPopup'>.
I cannot reproduce this locally.
Do you know what could be the reason for this since the expected and the found item have exactly the same name?
Thank you in Advance!
Such kind of errors occur when a Wicket component is made invisible after interaction with it.
For example if a user clicks twice on an Ajax link/button and the first click makes the component invisible then the second one will fail with this error.

Magento 2 giving error no category save. Error is - No such entity with id = xx

In Magento 2 We are getting error on category save. Error is - No such entity with id = xx please any one can help to resolve the same ?
Thank you.
click to see screen shot for error
It happened to me also, in version 2.2.0.
In my case the problem was the url_rewrite table.
Check the "metadata" column of the url_rewrite table for non-existent categories and delete those rows.
The problem are the url_rewrite rows of products belonging to that category.
Assuming your site is in Developer Mode, you can change it to Production Mode and clear/flush cache and then switch back to Developer Mode.
I had this issue in the front end, as i recently moved the datatbase from one server to another. I have managed to solve by this way.
Please make indexing and recheck. If you are using any third party extension then this issue also occur. If you have deleted any category from any store then this may also happen. Please check all things hope your issue will resolve.
Go to admin Marketing -> URL Rewrite
And search in the target path with specific id category or product where you have an issue.
Then delete the entry where entity with id = xx.
Go back your category or product page and try to save again.

How to resolve this error - " One of the documents you are trying to access has been deleted, please try refreshing"? in Odoo v8?

Whenever I try to create an employee record in Human Resources, when I click Save, the above error occurs.
I checked in the database for any kind of ir-regularities and found that I have attached the screenshot.
As in the database error, the Autoincrement ID has been skipped as I have noticed.
Anyone with a clear insight on this, kindly suggest with what can be done. It would really grateful. Thanks
Create a new database if you can, and re install your module and try again.
Ok I am answering the question,
There was a custom module which I was not aware of(other than my custom module) and that was installed. UNinstalling it removed the error.

How can I get rid of a persistent VBA Form Object that won't honor the form deletion?

I have an MS Access 2003 database that I'm using to develop a basic little inventory app. I have added some extraneous forms along the way and I wanted to get them out of the DB. I deleted most of them just fine but one of them appears to have left behind its VBA Object. All that's in the object is Option Compare Database. Now whenever I try to work with the database, I get the following error:
The form name 'Transaction1' is misspelled or refers to a form that doesn't exist.
If the invalid form name is a macro, ...
Truncated for typings sake.
Yes, I agree, the form doesn't exist. What confuses me so much is that all of the other forms, when I deleted them, also destroyed their VBA object as well. This one, no matter what, seems to like to stick around and I have no idea how to get rid of it.
How do I get rid of it?
Things I've tried:
Compact and Repair and the DB
Create a new form named what it's expecting, verify that it gets rid of the problem, and then delete that form.
You can try the /decompile switch
Make a backup of your mdb
Open your mdb (hold the SHIFT key down to stop any code from running) via a short
cut: msaccess.exe database.mdb /decompile
Open a module and compile your app
Save and close Access
Open again (SHIFT again) without decompile
Compact and repair database
close Access
I had similar problem. I found I had named the missing form in the STARTUP menu as the default form to open when starting Access. I opened Tools>Startup and deleted the missing forms name from the "Display/Form/Page" field of the Startup. My problem solved.
The problem I was having is that the form was named ~TMPCLP8151 and would not show up in Access no matter what I tried, but I could see it in VBA in the Project Explorer. Here's how I resolved the issue. I created a new form, and created an Event Procedure for Form_Open that contained this:
DoCmd.DeleteObject acForm, "~TMPCLP8151"
Then I just opened the form, and sure enough, the VB code deleted the form that I could not delete myself.
I had a same problem. I created a form with same name and deleted the form again. That fixed the peoblem. Try. BTW try to open the new form in design mode to make sure if the VBA module is assosiated with the new form.
I had to combine both solutions to achieve the goal.
First de- and recompile
next compact and repair
then create new form with the same name and delete it
Pay attention that the form has the status Hasmodule set to Yes
I had this problem. I renamed my default form from Form Login to frmLogin which suits my naming style, but the program was still looking for it on opening. I am using 2013 so I went to File » Options » CurrentDB and in the display dropdown select the new name. The old name remains in the list until you close and restart the application.