In Wakanda 1.1 I used "model.mergeSQLCatalog()" to see the MySql db that I was wanting to work with, as per the documentation. Trying to do the same in Wakanda 2, it tells me that that model.mergeSQLCatalog() is not a function. I get the feeling that I am missing something really obvious, but for the life of me I can't see what it is. Can someone enlighten me please? (I am working with a trial license)
model.mergeSQLCatalog() is deprecated since v2.0.0.
To keep working, add a SQL model:
Right click on models folder > new > model
Select MySQL
Set your SQL server config
A new model folder is created where you can put your old model.js file.
Here some official doc that can help you : https://wakanda.github.io/doc/#/guide?section=main-data-external
Related
enter image description here
How can I solve this problem
this is something related to your MySQL database not being fully compatible with Prestashop table creation SQL script.
If you can't overcome this by changing MySQL server , there's a relevant issue on Prestashop GitHub that should provide you useful detail to fix the issue.
Basically you can try this:
install/data/db_structure.sql
must be changed with:
CREATE TABLE ()...
... ) ENGINE=ENGINE_TYPE ROW_TYPE=DYNAMIC ...
so that the index size can be adjusted accordingly.
I was using dotPeek and my connection dropped right when it was going online to get some code for a given class. So my router has supplied it with 500 gateway page and now whenever I try to look at the code for that class I instead get an html view of that router page i.e. its been cached.
The problem is there doesn't seem to be any way to clear it. I've deleted everything in AppData for JetBrains for both roaming and local but to no effect.
Where is the disassembly cache for dotPeek?
For me, version 1.2 stores in C:\Users\{username}\AppData\Local\JetBrains\dotPeek\v1.2\DecompilerCache
Well thank heavens for process monitor. It stores it's cache in a directory like so:
C:\Users\rism\AppData\Local\Symbols\src\source.NET\4\DEVDIV_TFS\Dev10\Releases\RTMRel\ndp\fx\src\xsp\System\Web\Routing\RouteCollection.cs
In the latest version (2017.1.2), it appears to be in:
C:\Users{username}\AppData\Local\Temp\DecompilationTemp
I have been facing this issue for a couple days now.
It seems that on a client site I am recieving the automation error. The line of code in where im 90% sure it is coming from is below:
Set oTemp = New cPMXMLParser
However in other functions I seen
Set m_oXml = CreateObject("PMXMLParser.cPMXMLParser")
Which is essentialy the same except for the binding.
Please note both works locally but not on client site I was thinking maybe a dependancy is missing but seems not ... does anyone have any information on this?
Would
Set m_oXml = CreateObject("PMXMLParser.cPMXMLParser")
Be the best option?
I'm trying to install Magento 1.8, however I got stucked in configuration step.
I got the following message: 500 Internal Server Error
Looking log file I could verify the following:
SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'eav_entity_type' already exists"
But, here is the problem because it is a new installation and this table does NOT exist.
My Products versions are: W32 (test environment) PHP 5.4 MySQL 5.6.14 Magento 1.8.1.0, IE 9 FF 25.0.1 Chrome 31.0.1650
Could you please help me? Thanks a lot.
Login to your database using phpMyAdmin and make sure there are no tables in there.
If there are, drop the user/table and re-create it anew and re-try the install wizard.
Just delete all tabels or re-create databbase, and start installation again.
Today I finally got it. I did a totally new installation on Debian amd64. I installed only LAMP softwares and probably the FastCGI was avoiding to get success. It is necessary to confirm this.
I have been upgrading a joomla (2.5- to - 3.1) site locally but the upgrade is broken. The sql upgrade did not pass. I have been trying to use the database fix option but even like that did not get it to work in my case.
Database schema version (2.5.11) does not match CMS version (3.1.1).
Table '#__content' does not have column 'title_alias' with type 'VARCHAR(255)'. (From file 1.7.3-2011-10-15.sql.)
I have been trying to execute manually the other query but fails.
How could I fix my broken tables?
Where could I get a valid sql upgrade script?
Try clicking the "Fix" button on the Extension Manager > Database view. If this still does not resolve your issue, you'll need to manually apply all of the fixes. You can grab the SQL updates from GitHub (the same relative file path applies as well) and manually run each file's queries using a tool such as phpMyAdmin. Note you'll need to change the table prefix (#__) to match that of your own site.
had the same problem when doing upgrade 2.5.11 => 3.1.1, fixed it by first using phpmyadmin to add a title_alias field with VARCHAR(50) to #__contents table.
after which joomla added another complaint that title_alias should not exist in 3.0.
After applying 'Fix' I guess the old update scripts for 1.7 first changed title_alias to VARCHAR(255), then the update for 3.0 removed it again, updated the schema version in the db
and joomla stopped complaining...
Hope this helps you.