I have installed magento test Automation framework in local machine as below reference PDF.
http://www.magentocommerce.com/images/uploads/download/MagentoTestAutomationFrameworkInstallationGuide.pdf
All the installation setup has completed as per the reference.
After that i have added my project to netbeans. When i try to add the project in netbeans it seems error.
Below is the error message, which is i got from netbeans.
magento\app\design\adminhtml\default\default\template\catalog\product\attribute\js.phtml
This is my first try of Magento test automation tools. i don't know what was went to wrong.
Any help my appreciation.
Perhaps you can try changing a bit the directory structure
From
magento\app\design\adminhtml\default\default\template\catalog\product\attribute\js.phtml
To
magento\app\design\adminhtml\default\template\catalog\product\attribute\js.phtml
In my experience, Magento directory structure changes across its versions.
Related
The problem
So I am running into an interesting issue. I have been tasked to change a query for a simple SSIS package in Visual Studio 2015, which is a thing I have done multiple times in the last 6 months.
After changing the package and deploying it (to an installation of SQL server 2016, without errors!) I noticed that the execution of the package (scheduled with SSMS) generates the same result as the pre-updated package, meaning the demanded changes hadn't taken effect. Of course, as test, I have executed the package directly from VS2015 and got the result I wanted.
Ever since I have been running tests and trying to find a solution. The problems seems to lie with the receiving side of the deployment proces.
What I have tried
Deleted the package from the existing project in SSMS and redeployed. Deployment again seemd to succeed but the package didn't show up, so I had to restore an old version of the project.
Deploy the package from multiple different computers with access to VS2015 and the source code. No change...
Deploy the package to a new (empty) SSMS project: package does not appear in the project. This leads me to believe that the old package is kept when I publish the new version to the existing project in SSMS.
Regenating/rebuilding the package in VS2015, frankly this was never necessary and probably doesn't do anything for an SSIS package, but it may help you get an idea of my skill level.
In the past we have had issues with the encryption level blocking the deployment of packages. I have verified these settings and found no issues.
I have verified if any updates have recently been installed to the database server, which does not seem to be the case.
I have (of course) tried to google the issue, which is tricky due to the lack of errors. I have found the following links, that describe the same/a similar issue, but their solutions haven't helped:
https://dba.stackexchange.com/questions/259672/ssis-package-not-being-deployed
Deployed SSIS Package not reflecting changes made to package
What is still left to try
Rebuild project from scratch to see if that version is deployable.
Unfortunately I don't have a lot of experience with this subject and no colleagues or contacts to ask for help.
Thanks in advance.
My workaround
After quite a bit of time attempting to solve the issue I have resorted to working around the problem, by manually importing the .ispac file into the database. While this is not the prettiest of solutions, at least it's a workable one. If anyone has any other idea's I'll gladly see them, but for now the issue isn't nearly as pressing as it was.
From your post. "Deleted the package from the existing project in SSMS and redeployed. Deployment again seemd to succeed but the package didn't show up".
Are you 100% sure you are deploying it to the same project on the same server on the database? Are you refreshing after you deploy?
I have a Umbraco API project that using the UmbracoCms library V 7.15.3. The project work properly, but from some reason after that i copy the project to another computer. The API stop to work there and requests did not comes to the controller.
Is there a reason for something like this to happen?
Umbraco gives you a web application which you need to install and setup somewhere before it will work.
You probably used their installer initially which created an IIS website and a database for you. You don't need to re-run the installer, but you do need to copy the database and all the files and re-create the website in IIS on the other computer.
Simply moving files around is not enough.
So here is my Situation: Some company who hired me is still working with Zend Framework 1 and wants to move on to ZF3 someday.
So I need to learn how to work with Zend Framework 1.12 (for now). My job starts in 2 weeks and I am running out of time. The documentation on the official Zend Framework website showing me a 500 error.
Once I am typing "zf show version" on the linux console it shows me that version 1.12.20 installed, so far so good.
But once I type "zf create project zend", it claims that the project folder is created, but there's no skeleton in there.
When I try this:
composer create-project --stability="dev" zendframework/skeleton-application zend
...it creates a skeleton that looks like ZF3. I know there must be an "Application" folder.
What options do I have now?
Alright, after I rage-deleted the drive of the virtual machine and re-installed Linux I used the following tutorial: https://www.digitalocean.com/community/tutorials/how-to-install-zend-framework-on-an-ubuntu-12-04-vps
I can see the skeleton now.
I deployed a ASP.NET MVC4 app with SQL Server CE database, but I'm getting
Sorry, an error occurred while processing your request
I am using VS2012 to publish this app to azure website. How can I solve this issue? Thanks.
To summarize and so an answer can get marked on this to help the next person that comes by.
When running into issues on azure-web-sites FTP is a handy debugging tool which enables you to:
Verify that the dll exists in your bin directory
Sometimes the .gitignore file blocks directories from being checked in
Verify that your web.config file has the proper version of the assembly configured
NuGet can help, but it's ultimately up to you to verify your dependencies
Here is a good article to follow on the subject: http://www.dotnetcurry.com/showarticle.aspx?ID=883
Unfortunately with VS 2013 Compact edition is not supported any more, so things are somewhat tricky.
Friends Initially there was problem in the re installation of VS 2010 in my computer with Xp.
But i was able to install recently and every thing goes fine. I was able to use MVC 2 and other features. But when i tried to install MVC 3 i could not get success.THe installation process Roll back giving the message of FATAL ERROR DURING INSTALLATION.
Then i check in the error and found that Microsoft ASP.NET webpages 1.0 was missing in my computer.Is that the problem for installing MVC 3? or other .
I have attached the screen shot of error. I will be thankful for the solution.
Sorry, i couldn't upload clear picture.But Error shown was as follows:
Returning IDOK, InstallMessage_error[This product Requires Microsoft Asp.net web Pages 1.0. Please install the missing component, then try to install this product again.]
strong text
Using the Web Platform Installer will probably be the easiest way for you to solve your dependency installation problems. Using the installer will give you the ability to select and download/install a variety of products. For instance take a look at the follow screen shot:
Under the Products tab, you have the ability to select MVC3, ASP.NET web pages, MVC3 Updates, etc. Since some products depend upon others the Web Platform Installer will also manage these dependencies for you when installing your selected items.
Good luck, and hope this helps you some.