I have installed Magento version 1.9.2.4 and as per the PayUMoney documentation, I have pasted the "payu" folder into respective folder but still not able to see "payucheckout" tab in system/cofiguration/sales/payment method.
Why is this happening?
"Merge the files and folders in the PayUMoney module with the Magento module. In other words,
copy the end files/folders in the integration kit sent to you manually according to the files and folder
structure. For e.g.; the payu folder (path - app/code/community/payu) in the integration kit is
pasted in the following directory in the Magento folder – ww/magento/app/code/community/."
Merge Payu kit in magento root folder, clear cache and login again,
Enable module from here :
configuration -> payment method -> Payu checkout
Payu option will visible on checkout.
For test you can use details in admin:
Merchant Id: gtKFFx
Salt : eCwWELxi
Related
Intro:
Currently, I have two separate projects.
One solution is for .NET core Web API 2.0 and another project is Angular 6 app.
I have a problem deploying this to my hosting provider ( asphostsportal ).
It consists of one root folder httpdocs where when I publish my API I copy contents of publishing folder.
After transferring files via FTP I confirm that my API works by sending a request and getting the response.
Now I need to publish my angular project.
The simplest way to do so is with ng build and I get some folder in dist.
Problem:
If I transfer contents of the folder inside dist to my root folder httpdocs on server It can't find any page but API still works.
If I transfer the whole folder inside httpdocs and set server Host setting to define document root to that folder:
It will find the index.html and show me my landing page.
However then API won't work.
If I leave it as is and change the document root back to httpdocs ( where the API files are ) but push the index.html from httpdocs/website to httpdocs ( in this case I also edit index.html to point to website folder for resources etc ) in the hope it will find it ( server IIS setting )
It doesn't. After that my API starts working again. However, no landing page to be found.
Just FYI I do not have any extra startup.cs lines of code that have anything to do with static files nor did my publish command on API project create wwwroot folder ( like mentioned here)
Edit (Solution):
Okay, so I got it to work.
1) I added 2 lines of code in Configure method of Startup.cs in my API
app.UseDefaultFiles();
app.UseStaticFiles(); // For the wwwroot folder
Where according to MSDN
"With UseDefaultFiles, requests to a folder search for: index.html"
2) I manually added wwwroot folder which for some reason was not generating upon publishing command for my API project.
3) In that folder I copied all contents of my dist/website angular publish files
And now it works, cheers!
I have this laravel application on /var/www/html/application-folder/public_html
When I enter the apache server IP it doesn't load the laravel application instead it displays the Apache home page
How can I display the url /var/www/html/application-folder/public_html ?
When I type the full url I get the following error:
Forbidden
You don't have permission to access /folder/public_html/index.php on this server.
Apache/2.2.15 (CentOS) Server
If you have full root access to your server then you can
Step 1
upload your laravel project from the development machine(local) to the /var/www on your server - upload all folders except vendor and node_modules
Step2
once the project is uploaded, run composer install, if you need any of the node packages run npm install
Step 3
create virtual host for your site with DocumentRoot /var/www/yourProjectFolder/public
Step 4
Ensure storage folder has write permissions for your apache/webserver user - recursively
Step 5
Ensure that public folder has appropriate permissions - recursively, if you have uploaded the project as root then you will need to change the owner/permissions
Following this workflow you will be able to get your Laravel site up and running.
Important distinction to make here is that you have full root access to your server and that you can install composer and/or npm on your server before proceeding with the workflow.
If you can't install composer and/or npm on your server, then you have to upload the vendor directory to your server as well (and if you need any node packages then the node_modules as well) - following the documentation link in my comment above will help you.
Refer Virtual Host on Cent Os 6
I have my site up and running, but because of number of changes, i decided to publish an updated version. Before doing so i have made backup of my files and databases on the host, just in case.
Now this is what i did: Publish Nop.Web used FTP, configuration is set to release and from file publish options checked Delete all existing files prior to publish, as i was publishing to the same folder wwwroot. After publish was completed NopCommerce installation appeared (btw i would like to use the same db i used before) even tho settings.txt from the project I was publishing had the correct string path. I tried 2-3 times to pass the installation with no success (error: One or more sequence... something like that), checked settings.txt on the host and it was empty (no idea why), but i just edited it with the string path.
Now installation is gone i have my site running again with all the products and user information (i assume that means string path to db is good), but my theme is reseted to default, like all my changes to it (footer links, background, logo, favicon..etc etc) only thing that stayed as it should was the nivo slider widget that has the correct pictures displaying on this 'reseted' theme.
Checked General settings for theme settings if its the correct theme selected.
Also i have noticed this, i assume with those 2-3 unsuccesful install tried i have made some changes in db
http://i.imgur.com/wfXQYj6.png
Any suggestions how to sort this whole thing, before publishing i was running my site locally and it was good, i have backups of db and files(ones that i used before this publish)
I am using Nop version 3.4 and arvixe hosting. Sorry for my long post but i wanted to describe my steps and error as detailed as possible.
Thanks for reading and looking forward for your suggestions about this.
I haven't tried publishing features of NopCommerce version > 3.10, but you can try a more "manual" approach to make sure that files are properly updated on the server.
In short, you get files from your local machine which are needed for the built website and you upload them to your website folder on the server. You can make a backup and empty the server website folder first.
I presented that approach in this answer:
How to deploy nopCommerce 3.5 to new server from source?
You can check this batch script to see which files need to be sent to the server. The script also includes some suggestions about what else you may need to do to update the website on the server: https://gist.github.com/dan-mirescu/c14cc72e3f8ecca988b7
For Publishing the NopCommerce Application website below is the step:
Step : 1 - Publish the Nop.Web project.
Step : 2 - Publish the Nop.Admin project.
Go to the publish folder where your publish created
Step : 3 - Cut all dll from the Administration and Paste all dll to bin folder which in main bin folder for whole project
Step : 4 - Copy two things from your source project and in App_Data folder Settings.txt and InstalledPlugins.txt which is not published in your publish file so paste this two files in your publish folder in App_Data. (You need to change the connection string in Setting.txt as per your database host).
Step : 5 - Now you need to copy whole plugins folder from your source folder (but remember this plugins folder you need to copy from the Presentation folder not from the main source where the solution file are there.).
Step : 6 - Now your publish have been ready.(now you can deploy on hosting server)
I had to switch computers at work and my WEBMethods project was not moved to the new computer. After installing WEBMethods we noticed that my project had not been copied over.
So I went in to the laptop and found the folder that contains the webmethods project.
I copied all of the files in that folder along with the folder name to my new computer.
I know want to import that directory to WEBMethods (I noticed WEBMethods stores all of the information in a huge, huge XML file)
This is the folder that contains all of my files for this specific project.
Question: How can I get it moved into WEBMethods?
Here's an easy way to move your package:
1) Login to the webMethods administrative web console
2) Navigate to Packages > Management. You'll see a list of all the packages on your integration server.
3) Identify the packages related to your project and for each package click on
4) On the "Archive" setup page, leave everything as is except for the archive name. Name it to something you'll easily recognize.
5) At the bottom of the "Archive" setup page, click on the "Create Archive" button. This will create a zip file in the following folder
IntegrationServer\replicate\outbound
6) Copy the zip file to the new computer at the following location:
IntegrationServer\replicate\inbound
7) In the webMEthods administrative web console of the new computer, navigate to Packages > Management and click on the "Install Inbound Releases" link.
8) Select the zip file in the select box
9) Click on "Install release".
While copying packages it is always recommended to export the package and load it to new location. You can either use the Administrator Page to get the package or in case if you dont have Administrator access, then in that case you can use your developer/ designer to get the package. Follow below steps:
Select the package you want to move.
For Developer, click on File Menu(top left corner)>Export option to save the package on your current system.
For Designer, right click on the package you want to move. Select Export from Server option and save the package on your current system.
The package is now saved as a ZIP file. Copy the ZIP file to the new system.
In your new system, place the ZIP file to- IntegrationServer\replicate\inbound folder.
Open webMethods Administrator page and Select Packages>Management option. Click on Install inbound Releases Link.
Select the package name from dropdown and click on Install release.
In case you dont have Administrator access, you can pass the zip file to the person who has the access and they can follow the steps 5 to 7
If your package exists on an accessible server(A server you can login from your current machine), then open the server session in which the package exists. Also open the server where you want to place the package in the same Developer/designer. Using this way you can simply copy the package from one server and paste to other.
But while using this, make sure that dependent packages if any, exists in the target server.
Its always better , if you create the Release. Go to Publish link and create the full Build or patch.whatever you want, add the subscription to it and send it to remotes system via clicking send release link.
Would you please let me know how to update OJS (Open Journal System). I have installed it on a shared server and I have no access to the shell, only a web interface and control panel (direct admin) is allowed. I think there must be some update button online, But i could not find it.
Thanks
Download and decompress the package from the OJS web site
Make a copy of the config.inc.php provided in the new package
Move or copy the following files and directories from your current OJS
installation:
config.inc.php
public/
Your uploaded files directory ("files_dir" in config.inc.php), if it
resides within your OJS directory
Replace the current OJS directory with the new OJS directory, moving the
old one to a safe location as a backup
Be sure to review the Configuration Changes section of the release notes
in docs/release-notes/README-(version) for all versions between your
original version and the new version. You may need to manually add
new items to your config.inc.php file.
The easiest thing would be to make a new folder on your shared hosts with the latest version. Copy over the config.ing.php, cache, and public folders. If your files is within your OJS folder as well, copy it too (though, you should move it outside the web accessible location).
Then you'll find an option to upgrade the database in the Admin pages.