I removed an extension from RefineryCMS but the tab for that extension is still in RefineryCMS admin area.
Most engine installs come with a database migration. Look in db/migrate and identify any migrations associated with the engine. Then:
rake db:migrate:down VERSION=<number of migration to reverse>
try to use this:
rails destroy refinery:engine [refinery-engine-name]
Related
I recently tried to create an FAQ Page with the TYPO3 extension jpfaq.
I did set up everything as it was described in the manual. But for some reason when i preview the page, it shows a bunch of different error. For example:
TYPO3\CMS\Extbase\Persistence\Generic\Storage\Exception\SqlErrorException
Table 'xxx_typo_dev.tx_jpfaq_domain_model_ttcontent' doesn't exist
When I "unbind" the FAQ database I created it shows me the correct FAQ page (just without the questions and answers). So there might be a problem with the database?
Cleared cache. Deleted and installed the extension again. Didn't help.
Sounds like the you need to fix the Database Structure.
Normally the Database Structure is fixed when you install new extensions in the Extensions module.
If you use Composer Mode the installation is done with composer and you need to fix it by hand.
This can be done in the InstallTool / Maintenance Module: Analyze Database Structure.
Or you use the commandline: vendor/helhum/typo3-console/typo3cms database:updateschema (don't forget to use composer require helhum/typo3-console)
I have a composer typo3 (8.7.30) project, but somehow the extension-manager does not show up.
I tried the following:
./vendor/bin/typo3 extensionmanager:extension:install extensionmanager
./vendor/bin/typo3cms extension:activate extensionmanager
./vendor/bin/typo3cms extension:setup extensionmanager
My user has admin rights and I can see other admin tools. I also tried to create a new admin with the install tool and the new user had the same "problem".
Other modules - including custom ones - are showing up.
Any ideas on how to tackle this?
Edit: When I install the project step by step without generating the package state it's working fine, but the moment I generate package states the extension manager is missing - even though the entry in the PackageStates.php
One userTsConfig.ts disabled the module in the production context. I didn't check for it because the behavior was new for me. It was neither a typo3 or composer problem, just a configuration issue.
After installing from your composer.json, the extension manager is available.
I guess that your PackageStates.php just somehow misses the extensionmanager:
'extensionmanager' => [
'packagePath' => 'typo3/sysext/extensionmanager/',
],
If I manually remove that section, vendor/bin/typo3cms install:generatepackagestates (from the package helhum/typo3-console which you already have installed) would regenerate it.
Is it possible to automatically create migration files when using sequelize?
For example if I change my model, is there a way to automatically create a migration file that reflects those changes and run the migration to effect those changes in the database. Or do I have to manually create migration files myself?
I am using PostgreSQL.
There is a package for that
Sequelize-mig
its maintained and documented.
Install it with:
npm install sequelize-mig -g / yarn global add sequelize-mig
then use it like this
sequelize-mig migration:make -n <migration name>
and it will generate the migration file
I highly recommend Sequelize-mig, as referenced by MRVMV. I have 25 years of experience in creating my own ORM, and for my most recent project I decided to finally use an existing ORM. I chose Sequelize and as I got going with it, I was sorely disappointed that it does not have the ability to automatically genereate migration files by inspecting model files. This issue landed me here in this SO thread, and so I tried sequelize-mig. I read the docs and tried it out for about 4 hours and I find it to be working very well.
Using it, you can just create/modify your models .js files, then call "npx sequelize-mig migration:make --preview" to see what it will do. Carefully inspect all the preview code and make changes until you love the result. Then call "npx sequelize-mig migration:make -n <>" and it will populate the migration files. Carefully inspect those and when you love them, then use sequelize to migrate to your dev database by calling "npx sequelize-cli db:migrate" and that's it.
Next up, I will decide upon the best way for moving these migrations to production. But that decision doesn't have anything to do with sequelize-mig - it is the same decision you have to make for sequelize itself, just that now you get automatic generation of your migration files, thanks to sequelize-mig.
Highly recommend sequelize-mig!
I want to migrate the schema of my models. I wanted to try to do so with the "migrate: alter" command in my env file.
The problem seems to be that on default the startup script will run in production mode which automatically uses "migrate: safe".
I´ve tried changing the "migrate" attribute to alter in die production.js file which does not take effect. Also I tried to set the environment variable to development but it will still start in production mode.
If you have simply installed sailsjs globally with npm, you can try cli command,\
sails migrate
to migrate the database. This is confirmed by sailsjs on twitter.
Help is requested to delete a database I have created in TYPO3 setup.
I have installed XAMPP in Ubuntu 16.04 and configured it correctly and it runs. Now I was in the process of configuring TYPO3 in XAMPP using this very good guide.
After creating the "typo3cms" database, the next stage asked for a user name and password. I think I was supposed to put in my Ubuntu username and password, but erroneously I put in a new username and password and got the error of not being able to connect to my database.
I tried to go back to the previous stage of creating a database, which I can't because it already exists. But then I cannot go forward anymore. I have no idea where the database resides so that I can delete it and recreate it. I have tried uninstalling typo3 and reinstalling it. I have tried to google the problem without success.
Short of purging xampp completely and starting from scratch, is there a way I can delete the typo3cms database I have created?
It sounds like you are so early in the install process that you can start over (by removing all files and doing the install from the beginning).
Alternatively you should be able to remove typo3conf/LocalConfiguration.php and make sure that FIRST_INSTALL exists in document root (this is an empty file used to indicate that TYPO3 is doing the first install, it gets removed after - and you can use touch FIRST_INSTALL in terminal to create the file). Or if you prefer a completely manual approach, manually edit the typo3conf/LocalConfiguration.php file to correct or remove the database credentials and then resume the install.