I have a bug_fix.patch file for Joomla version 1.5.22 and I am trying to apply it. How does one go about doing such a thing?
One article I read mentions dumping it into the root directory of my Joomla site... But how is it picked up by Joomla? It doesn't make much sense to me.
Thanks in advance.
If you are trying to upgrade your Joomla version (which it sounds like you are) then you should download something like "1.5.22 to 1.5.23 Upgrade Package" from http://www.joomla.org/download.html.
You then unzip it and upload all the files.
The bug_fix.patch file is for developers working on the Joomla project, see http://jungels.net/articles/diff-patch-ten-minutes.html for an example.
Related
I saw someone "extending" an existing viewdef by simply copying the stock file into the custom folder and then modifying that copied file.
It makes sense, but I don't see that in official documentation.
Example modules/Leads/metadata/editviewdefs.php copied to custom/modules/Leads/metadata/editviewdefs.php
Is this safe/correct way of doing it?
That's the correct way to do it.
A quick reminder about future SuiteCRM upgrades and view/edit-defs.
Sometimes newer SuiteCRM versions add/edit fields to modules and the upgrade process will not upgrade your copy of those files, sometimes causing weird errors.
If you have access to a Backup is more easy to copy the file from there and then edit it with a new Uploader Package.
When i trying update kentico to 10 version i have a some problem:
"the selected folder is missing a vital kentico component"
but I'm sure I chose the right folder. Who mean why?
It looks as if you are attempting to use the Kentico Hotfix Utility to upgrade from v9.0.50 to hotfix v10.0.41, which is not supported by Kentico. You cannot use the Kentico Hotfix Utility to upgrade Kentico from one major version to another. You need to:
First upgrade the project from 9.0.X => 10.0 - upgrade documentation available at https://docs.kentico.com/k10/installation/upgrading-to-kentico-10
Then you will need to run the project.
Then you can apply the latest hotfix utility - available at https://devnet.kentico.com/download/hotfixes
Then run the project again.
I appreciate you had a missing lib folder, but even if this were present, you still can't perform a major version upgrade using the hotfix utility.
I think in your case, you only have the CMS folder from deployment. But the upgrade needs the Lib folder which was not needed for deployment.
What you can do is to find the Lib folder from another instance or just install V9 of CMS, and you can find the missing Lib folder in C:\Program Files (x86)\Kentico\9.0\Webinstaller\Web
Few things can cause this:
Customized core files
Missing dll's
Changes in the web.config which cause Kentico references to be broken
and some other issues, but these are the most common we see.
Have you tried to open the project within Visual Studio and build the project? Secondly, are you selecting the directory with the CMS and Lib directory in it?
Does your project has the default structure or is it loke it was installed to the root of the web site? Default structure is some folder and underneath are the CMS, Lib and also the .sln file and few others. Looks like you have just the content of the CMS folder. In this case you either need the original project or upgrade the manual way.
You may also run CodeUpgrade tool from Kentico
Basic detection
Run CodeUpgrade.exe from the command line, with the path to your project’s solution file as the parameter (WebSite.sln or WebApp.sln).
For example:
CodeUpgrade.exe C:\inetpub\wwwroot\Kentico9\WebSite.sln
The tool generates a csv file containing a list of custom code occurrences in your project that are no longer valid in Kentico 10. The information will help you update your custom code after you perform the upgrade.
Source - Kentico documentation The documentation has all the commands to run and detect the incompatible code. This might help you.
Kentico 9 to 10 Upgrade tool - http://download.kentico.com/CMSUpgrades/Upgrade/Upgrade_9_0_10_0.exe
Basic steps to ensure before you perform upgrade - https://docs.kentico.com/k10/installation/upgrading-to-kentico-10
I am having trouble setting up the testing mentioned in the title because of the folder structures for Xampp and Git/EGit respectively. Can anyone recommend a guide or tutorial on how to do this?
Given Xampp is looking for the .htdocs/appname/ folder for testing the app but folder structure can be something like .htdocs/repositoryname/appfoldername, they are hard to match. Has anyone solved this?
Or should I be testing with some other software which is suitable for testing PHP projects in Git repositories?
You could make a symbolic link (even on Windows) in order for .httdocs/appname to refer to .htdocs/repository/appfoldername (with option Options FollowSymLinks set in the <Directory> section of your Xampp httd.conf file)
The OP alieninlondon reports:
I found another very easy way.
Simply by putting the repository directory in the .htdocs folder and then accessing the app through localhost/repositoryfolder/appfolder in my webbrowser worked perfectly for me.
I have no idea what I'm doing -
Where do I put the dotcloud.yml file?
There isn't much help on this for people who don't knwo what they're doing. Insturcitons just say create the file.... where do you put it? In my pictures? In my documents? In a new folder called "pics of mj" on my desktop?
The dotcloud.yml file will generally be located in the directory containing the code of the application that you want to deploy on dotCloud.
I would recommend to check the dotCloud tutorials, e.g. http://docs.dotcloud.com/firststeps/quickstart/ ; I think it will explain all you need to know :-)
If you are referring to a specific guide or tutorial, don't hesitate to mention which one—if it's a doc maintained by dotCloud, they will certainly update it!
Probably in the root of your app/project directory, that's where I have a config.yml in a Ruby project. You can see an example of an yml file in the repo linked below.
https://github.com/ramaze/ramaze
I'm unfortunately not familiar with that deployment platform? So I'm not sure what the zoom command would do in that prompt.
For ruby it looks like the deploy command is dotcloud push [foldername] in the prompt.
http://docs.dotcloud.com/services/ruby/
There is a hint in the dotcloud.yml docs, but you're right, we need to make the location more explicit.
The dotcloud.yml file must go at the root of your source tree.
I have created a web part using VSeWSS 1.3. It creates a wsp file and my web part gets installed, everything works great.
I would like to also create a folder in the LAYOUTS directory of the 12 hive and place a couple files in there. How do I go about doing this? I know that I can manually place the files there, but I would prefer to have it all done in one fell swoop when I uses stsadm to install my solution.
Is there a best practices guide out there for using VSeWSS 1.3 to do this? They changed a bunch of stuff with this new version and I want to make sure I don't mess anything up.
You can create a new folder structure in your webpart project, like:
Templates/Layouts/CustomFolder and put your files in the CustomFolder directory and include them in your project.
When you go to the WSP View in Visual Studio, you can see in the manifest.xml that your files are being included in the deployment.
I have done this successfully on multiple projects now.
In case anyone is wondering, the VSeWSS 1.3 user guide is incredibly helpful. It is installed to the same directory as the tool itself, default in C:\Program Files\Microsoft SharePoint Developer Tools 9.0\VSeWSS13.CHM
You can see a working example with screenshots Here
A simple step-by-step tutorial for the above, along with deploy/retract scripts is here at Add New Files To 12-Hive Through A SharePoint Solution. Just follow the steps and in a few minutes you'll be able to add whatever you want to the 12-Hive!