So I've installed an extension in my Magento Enterprise.
I've been able to configure new options in the admin interface after installing the module.
However in the frontend it complains "table not found". Checking the database that is indeed true. Seems the mysql4-*.php scripts have not been run or failed.
Is there a log or something I can look at to see what goes wrong? From what I've read (difficult to find documentation on this) the modules db should've been initialized on the first request after it was installed and activated.
Any other suggestions to what I can check to find out why it's not initialized properly?
First step is to check the core_resource table. If there's a row for your module, then zap it. This will retrigger the setup resource process.
Related
i want to try new atk4 4.3 version. I know its still in development, but my hands itch ;)
So i found this, and i thought this is good bundle to start with?
https://github.com/atk4/agiletoolkit-bundle
I cloned it and used ./update.sh, but i get this error:
Cloning failed using an ssh key for authentication, enter your GitHub credentials to access private repos
The credentials will be swapped for an OAuth token stored in C:/Users/wechta/AppData/Roaming/Composer/config.json, your password will not be stored
To revoke access to this token you can visit https://github.com/settings/applications
But if i remove this lines from composer.json it gets to the end:
"rvadym\/languages":"dev-master",
"rvadym\/x_tinymce":"dev-master",
"rvadym\/blog":"dev-master",
is this the right package to start playing with atk4 3.4, or what im doing wrong? im using all this stuff the first time on windows, so there is a lot of not knowing.. Thank for help!
The bundle is currently not fully available through GIT. If you do want to follow our internal development, then:
http://www4.agiletoolkit.org/
and click download. You can also check periodically:
http://www4.agiletoolkit.org/changes
I’m running CKAN 2.2 on Ubuntu 12.04 LTS (GNU/Linux 3.2.0-23-generic x86_64).
I have uploaded a dataset to the CKAN instance. It has been uploaded successfully and can be downloaded as well. But when I try to preview the database I end up with below error.
This resource can not be previewed at the moment.
When I click on the “Click here for more information”, It says
Could not load preview: DataProxy returned an error (Request Error:
Backend did not respond after 10 seconds)
How can I fix this error?
The problem is that the data proxy (which is used to transform csv to
something that the data preview can understand) is a server on the
internet. Consequently the files you want to preview have to publicly
accessible from the internet as well. localhost is your own computer
which means that the dataproxy cannot access it. To solve this, wither put the file in the datastore using the datastorer or put the file on a server and provide the correct url.
.
This happens because the data proxy which is used to transform the
data into something we can preview with recline needs the files to be
accessible from the internet. The best solution is to store the data
in the datastore and then the preview will work.
Extracted from here & here
Sometimes you get the same message as the title question:
This resource can not be previewed at the moment.
But when you click on the “Click here for more information”, It says:
Could not load preview: DataProxy returned an error (Data transformation failed. error: An error occured while connecting to the server: DNS lookup failed for URL: http:///dataset/c3ce226b-73bd-4b06-9d1b-ffea13d5f770/resource/580fb05f-6d86-4748-aac7-560b904a208f/download/foo.csv)
In this case, probably the datapusher plugin is not working. First follow the instructions for datapusher in CKAN manual. If you already did this or you installed CKAN from a package, check the CKAN configuration in production.ini (development.ini) file. A small check list to solve the problem:
add datapusher in "ckan.plugins"
set "ckan.site_url"
set "ckan.datapusher.url"
check Apache/nginx server logs (/var/log/apache2/datapusher.*.log, /var/log/apache2/ckan_default*.log)
In my case, the issue was in my development.ini (or production.ini for you maybe) file where the lines for DataPusher's configuration were commented out with a # in the start of the line. Also, the ckan storage config line was also commented.
I uncommented those lines and it was solved.
I added a DataContract to my service and tried updating the service reference to get access to that DataContract. But it never showed up in the intellisense. I cleaned and built the project and then updated the service reference, but it still didn't work.
I then published it to the server and updated the service reference so it would point to the server, but I get the same thing. I browsed the service through IIS and opened my service in the browser.
I clicked the top link that had Service.svc?wsdl to see if my DataContract was there. An old MessageContract was there, but the DataContract was not.
Any ideas on what I'm doing wrong here?
Delete the currently deployed service binaries and verify that the service is inaccessible. Then deploy the new service binaries. This is to verify you're actually deploying to the correct location.
It is also possible that the service binaries aren't being rebuilt. To verify this, delete your bin folder (located next to your project file generally) and issue a rebuild, then follow the first steps.
I got my answer from here.
Only the types actually used by the service will be reflected in the metadata.
I didn't have an operation contract that used the DataContract. I didn't need to have one at the time, so I didn't make it. But apparently, unless you have one that uses it, the metadata won't be generated for that DataContract.
In our team, we use a common database server. When running the Orchard Setup, I point the connection string to an existing Orchard Database and got this error message:
Setup failed: The requested service 'Orchard.IWorkContextAccessor' has not been registered. To avoid this exception, either register a component to provide the service, check for service registration using IsRegistered(), or use the ResolveOptional() method to resolve an optional dependency.
The only way that can make setup successful for me is to point to an empty database. I attempted a workaround by doing so first, and then edit connection string in App_Data\Sites\Default\Settings.txt, but then I got the same error.
I had this problem as well, also tried copying the settings.txt file which did not work. This time I copied all the contents of the App_data directory over and it worked for me. Also, this latest time I was using the latest commit from codeplex.
I deleted cache.dat and restarted the website in IIS, this fixed it for me
i am looking into upgrading my magento community from 1.6.2 to 1.7.0.2.
First i will do this on my test server, but there are some errors during updating in magento connect, so i have to upload some files my self ...
but when i going to put these data into the live environment, can i just simply copy my data from the ftp to the live website?
Or are there also some new/changed settings in the database?
And if yes on the last question, which lines are changed?
I was able to successfully upgrade Magento from 1.6.1 to 1.7.using Connect Manager.
Here are the steps I had foung and followed
Go to yourdomain. com/magento/downloader/ (of course, make this
match your installation’s path.
Because I had installed Magento using tar.gz package provided with a skin I wanted to use, Magento Connect didn’t have all the
extensions listed for upgrading. I had to type
“connect20.magentocommerce.com/community/Mage_All_Latest” in the
“Install New Extensions / Paste extension key to install”
If you run into an error along the lines of “CONNECT ERROR: Package ‘Mage_All_Latest’ is invalid” repeated several times, once
for each package, it is because the files already exist, and you
have to remove a line of code in order for it to over-write data.
After everything has updated, you will probably have some errors. Make sure you clean the cache and session directories (delete
everything in /var/cache and /var/session)
If you receive a “500 Internal Server Error” it is more than likely because of file and folder permissions. It took .5 sec to
reset all of the permissions to what they needed to be.
If you receive a “Service Temporarily Unavailable The server is temporarily unable to service your request” error on a Magento
formatted header, it is probably because the store is set to offline
mode to prevent visitors from screwing up the installation process.
To fix this, delete the“maintenance.flag” file found in the root of
your magento installation directory.
Everything should be ready!
Avoid upload core library changes via ftp.
The fastest and more secure way is to patch your application using the diff files
patch -p0 -f < 1.6.2.0-1.7.0.0.diff
Then when you first visit your site Magento will automatically upgrade your db
best way to update is get a fresh mage zip 1.7.1 or whatever, and connect it to your current DB. When you go to index - the new install will update your DB to the latest MAge DB. This way you dont have to use connect etc. The mage zip has its own sql updates.
Make sure you put your current theme into the new install etc, and test it 1st on localhost etc.