I am getting Database update message continuously like below
Database Update Required
WordPress has been updated! Before we send you on your way, we have to update your database to the newest version.
The update process may take a little while, so please be patient.
Update WordPress Database
I have searched for it and found that a broken theme may be the cause of that. My theme is also showing message that
The parent theme is missing. Please install the "Template" parent theme.
This message is surprising for me Because I am not using child theme. I haven't mentioned anything about parent theme in my style.css.
But one time parent theme issue resolved on its own for few seconds But after that it starts giving message again. I have no idea why it is happening.
Related
I recently downloaded Web2Project after going through the reviews. Installation was a breeze and the application is neatly aligned. I was able to create the users, assign permissions, create companies etc.
However when I am trying to create a project , despite filling all the fields in the screen the page just refreshes back without giving any error message or creating a project.
I am looking to see if there is a way to troubleshoot what is going on with the page. I tried exploring to create an account in Web2Project support forums but not able to create an account through the available media and hence seeking technical assistance through Stackoverflow.
Web2Project New Installation
Web2Project Code (Just installed on WAMP Server) -- Projects Module
After filling all the fields in the Project Screen, the project should be created.
But the screen just refreshes without creating the project. No errors shown. When I go to Project List page nothing is created.
I was facing same problem. Took a lot of work until realized that the cause was the field PROJECT_ID of the table PROJECTS was not created with the auto increment definition. I just seted up this property and the problem was solved.
How did i discover the cause of the problem? In the SYSTEM ADMIN module, access the SYSTEM CONFIGURATION page, and then set the value of the field DEBUG LEVEL to 1, and check the field SHOW DEBUG MESSAGES. This will allow the web2project to log into C:\Windows\Temp\PHP72x64_errors.log (in case of my instalation) the error.
Good luck!
I'm facing the same problem and took a lot time to solved until I came here.
Goto the table project immediately, found no auto_increment in project_id field. Put it on, it worked!
And hoping current web2Project maintainer will fix this in their installer.
Thank you!
I have installed a new theme called Express (pt_express) from Magento and I am having issues. I keep getting "There is a problem with the reindexing process" when I go to reindex all the files there. The one called "PT Express" (that got created when I made the theme) is the one that cannot be reindexed. When I tried to do it via SSH I got this:
PT Filter index process unknown error:
exception 'PDOException' with message 'SQLSTATE[42S02]: Base table or view not
found: 1146 Table 'justind1_direct.filter_attribute_url_key' doesn't exist'
in /home/justind1/public_html/lib/Zend/Db/Statement/Pdo.php:228
However, everything else indexed fine.
I looked in phpMyAdmin and I know the table isn't there, but I don't know how to create it. How do I create this table so it exists?
The table
`filter_attribute_url_key`
is not part of any stock magento system I've heard of. That, plus the fact that googling for that table name only brings up this ticket, point to this table (and problem) being
Part of a module that came with your theme
Part of some custom code you have on your system that's interacting poorly with the code that came with your them
I'd look at the modules that came with your theme -- particularly the sql folder. These contain setup resource files (migrations) that should automatically run if you load Magento with an empty cache. That's normally how modules add new needed tables.
You also might try asking your vendor for support.
Without more research you're unlikely to find an answer here, given the very specific nature of the problem and the known state of your specific system.
I am new to Drupal and have been experimenting with some free themes. After installing one free theme called 'tb_sirate' my site is throwing exceptions and my admin controls are no longer available, just a page full of exceptions. Unfortunately, there is no obvious way to undo this.
It seems I have two choices to rectify this. First (and hopefully this is not my only option) is to start over completely. Second, if I could find where the theme is referenced in the database, I might be able to change it back to a known working theme.
Can anyone offer and advice on how to fix this? Anyone know where in the DB the themes are referenced?
Thanks! Viv
Don't worry there are only 3 simple steps to recover your site. Here are the steps and corresponding SQL queries you can run. If you run the 3 queries this will change your default theme from the "tb_sirate" to "bartik" the Drupal 7 default.
1) In the "systems" table change the status to "0" for the record that represents the defective theme. Note that there is one row here for each module/theme. With the status variable "0" means disabled, and "1" means enabled.
UPDATE system SET status=0 WHERE name='tb_sirate'
2) In the "variable" table find the key "theme_default" and change it's corresponding value to the theme that you want to use.
UPDATE variable SET value='s:6:"bartik";' WHERE name='theme_default';
3) Drupal caches these values so you will need to clear the "cache_bootstrap" table for the changes to take effect.
TRUNCATE TABLE cache_bootstrap;
To avoid similiar problems and to able to have peace of mind regular database backups are essential when doing Drupal development. The backup and migrate module can help with that.
I have been working on a huge ETL project with 150+ tables and during the design I had to make a major change on destination column names and data types for a couple of tables.
My problem is that I can't get SSIS to see the new schema for the tables I changed. So I would like to know how can I get SSIS to refresh this schema? I find it kind of ridiculous that there no way to tell SSIS to update the metadata from database schema, especially for database migration.
Recreating the project from scratch is out of question because I already spent some hours on it. Also changing manually the 400+ columns I changed is also not an option.
What about using the Advanced Editor and pressing the Refresh button on the left side below?
Following my previous auto-answer, I finally found what was preventing the metadata from being refreshed.
When I originally modified my database, I actually executed another script that was making a DROP on the table and then a CREATE TABLE to recreate the table from scratch. There, SSIS was never able to detect changes and I had to do all the things in my other answer.
Later today I had to make some minor modification and this time I opted for an ALTER TABLE. Magically, this time SSIS detected all the changes even notifying me to refresh columns from the advanced editor, which worked fine.
So basically all these issues has been caused by my poor knowledge about DBA and its best practices.
I found a way to fix it but that was a bit tricky.
Even thought I was completely removing any references of the table from my packages, I was always getting the old metadata.
I still don't have a clear fix but here is what I did to fix it:
Removed any reference to concerned source and destination tables
Deleted obj and bin folder from the project folder
Saved, closed and then reopened the project
Created new data flow from scratch and updated metadata was finally there
Don't know where those informations were cached but I suspect that the obj folder keeps a cached copy of your packages or that Visual Studio keeps metadata in memory which is freed when you close it. Anyway, following these steps should fix it.
I had a working project in eclipse which created a JPA table from entity to mysql database (still learning). Unfortunately it made the table in the wrong database as I wanted there to be 'test' and 'production' databases. Somehow it got the details for the 'production' db, even that it looked like the selected database connection was for the test.
I tampered with the project a bit and made it to connect with right connection object for certain (test). I can ping the db in eclipse (both dbs) and see the db in the Data Source Explorer.
But now I can not create the table(s) for the project by right clicking on it and selecting 'JPA 'Tools' > 'Generate Tables from Entities'.
The creation starts and finishes with no errors, like everything works, yet I see no tables in either of the databases. (In eclipse Database explorer or from command line).
The persistence.xml should be fine as it already created that one table before.
The only error is for the Entity class as it says for the Entity annotation "Table xxx cannot be resolved". And as I see, it's coming from the table not being created.
Here's the persistence.xml just in case.
http://pastebin.com/djPZei90
The project is also a Maven project and it uses SVN. The dependencies were successfully loaded by the maven for the eclipse/project and there is no complications with the SVN.
Because of Maven there are 2 persistence.xml files (only the login credentials and the database name changes), for production and test. It could be that the db-connection was checked and loaded from the wrong file at the 1st place. (just guessing)
Also I tried to create the script.sql when generating the table(s). I found the file but it was completely empty.
Anyway the problem is now that I can't create the tables anywhere.
I am totally puzzled by this. Any hints where I should look to fix this?
Chris had it right, even that I didn't understand the answer correctly at the first reading.
I tried with the other provider, but I may had modified the wrong file by accident (2 'persistence.xml' files as it's a maven project), or there may have been some other reason I failed to spot.
I was given a hint earlier, that I should use the given provider (in persitence.xml). Causing that I didn't pay too much attention to it after all. Since using eclipselink, the provider has to be indeed:
<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
Thanks again Chris, even that I failed at the first attempt and had to spend several more hours on resolving this.
Could you solve the problem? Unfortunately I have stumbled on the same rare issue, which totally makes no sense. The JPA Tools just doesn't add the mapping classes for whatever reason, although it writes them into the persistence.xml.
Previous week everything worked flawlessly but now everything is f**. I even created a new independent project in different workspace but it happens the same bug. Obviously it's an eclipse/plugin bug, otherwise I can't explain it. Working with eclipse 4.2.0. I am not happy.
Edit: After removing Dali Tools, JPA Configurator, Seam 3 Plugin creating entities seems to work again. Don't know why, most likely a conflict, but it still doesn't explain why it happened now and not 1 month ago. I didn't change my eclipse install at all since then...
Spend the whole day on this.
I created a completely new (JPA) project in Eclipse (Indigo btw).
Also created a new database (mysql) for that.
Made a connection in Eclipse for that. File > New > Other... > Connection Profile.
Made a new package structure and let the Eclipse create the 'persistence.xml' (src/META-INF/persistence.xml).
I made an 'JPA Entity' class with eclipse wizard. (added 'id' (PK) and 'content' fields)
Copied the 'pom.xml' from my previous project to the new one (made only minor changes like the project name).
Also copied the 'persistence.xml' file from the previous project (src/main/java/META-INF/, no 'test' included). Changed database details and login credentials from the persistence file.
Made the project 'Maven project' in eclipse (right click on project name > Configure)
As it was now a Maven project the default 'persistence.xml' could be removed as it was in wrong place. (Mavenizing the project removed all the errors from un-existing jars with the pom.xml)
Tried to create the table again for the project (Same error, but wait...).
Right clicked on project > Maven > Disable Maven Nature
Then again made it maven project, right clicked on project > Configure > ...
Tried creating the tables again and it created them. Everything works!
Go figure!
Seems like everything was ok, like I suspected. There seems to be some sort of bug with maven (plugin) + eclipse.
Doing the same tricks on the previous project won't help. I even created the entity class with the wizard (removed the existing). The <class> declaration is added to the 'persistence.xml', but it still wont do the table. (Also tried removing and re-adding the maven nature)
I could be missing something on the process/did it differently or doing it wrong whole together. But considering I get the other project work while other doesn't, using the same tricks, there seems to be a big nasty bug.