I'm using Magento 1.4.1.1, and Maison du Logiciel's extension Embedded ERP 2.7.5.6.
Apparently I need a MagentoClientComputer.xml file but it's not included in the EE-2.7.5.6.zip package at all! I looked it over more than once and I looked at the installed files of the Magento Client Computer program and can't find it at all.
What am I supposed to do? What do I need to be able to configure the Client Computer settings on the server?
Maison Du Logiciel split the Client Computer program into a separate package that must be downloaded separately from their forums.
you probably didn't ask Maisondulogiciel because they would have told you to download it on maisondulogiciel support forum using your credentials
Related
Have coded webpages on Cloud9(Laravel installed. Not AWS but https://c9.io) and now want to publish pages. I already have spaces in rental server to deploy but don't know transfer data from cloud9 to server nor how to setup server.
Please let me know if you know how to transfer data and setup server. Also welcome share URLs that explain these FAQ. Thank you in advance.
(Googled these keywords but not found any useful expalnation. Keywords:ssh,ftp,laravel,cloud9)
Found solution from my tutor advices. Downloaded files from cloud9 and transfered to server by FileZilla. While doing this, have to modified some files to be adopted to server but it was not a big deal.
Now I think I have to use AWS cloud9 or similar services to deploy works more easily.
Hope this comment help somebody stacked.
i have a curious issue. When i start the connect manager i see a white window with the following error message: svwrap $Revision: 1.36 $
Error #619 security: script is world-writable
Does anyone have an idea what could be? I know what "world-writable" means but what file it might be? Thanks for an answer. Hermann
I'd contact your hosting company this. This message isn't generated by Magento, it's generated by a program your web hosting company has installed to scan for world writable scripts.
Also, you may want to consider a different web-host if you need to use Magento Connect's web UI. This feature requires the Magento web server user have write access to the Magento installation to download and update files. It sounds like your hosting company may not be down with that.
All that said, my guess is it's, at minimum, the downloader/index.php file.
My Joomla 2.5.4 site was cracked last night. Moreover, the Joomla forum is currently down, and I can't even run Joomla's diagnostic utility. (fpa-en.php)
I have followed Joomla's instructions for diagnosis with no success. (See below) I have also emailed my webhost (I am on a shared server, but I use a host recommended by Joomla that is a specialist in Joomla sites). So, my question is what do I do next?
Here is the info that I have so far.
Using Joomla 2.54 (the latest). All extension were updated to most recent release, and none are on the Joomla vulnerable extensions list.
Passwords of other administrators were changed but not mine fortunately.
User_notes table deleted, which renders the User Manager in the admin section useless.
According to logs the attack hit the following files in this sequence:
/administrator/index.php
/index.php (Root)
/plugins/authentication/joomla/joomla.php
/plugins/user/joomla/joomla.php
and then the changes to the users and user_notes tables.
There is no junk in either index.php
Attack ip was 199.15.234.216, which is from a Fort Worth server of supremetelecom.com
Fortunately, I have backups and there was no defacement, but until I can't get fpa-en.php to work and access to the Joomla forums, I am not sure what to d0 other than change all passwords and block the ip.
Thanks in advance for any help!
Firstly, reset the passwords of all the administrators, including yours, then change them and ensure they include letters and numbers. Then change the password for the host control panel using the password generator if they provide one. If not, use a password generator online. Once this is done change the password for your database username and don't forget to also update the configuration.php with your new password.
Secondly, download and install Admin Tools which will add more security to your site for the future. Admin Tools also comes with an Emergency Offline button which is useful.
Then download and install Saxum IP Logger which will trace all the registered users, giving you their IP address, country and so on and you can also block IP addresses using the plugin that comes with it.
Next, go to the host control panel and look at the logs to see which IP addresses have entered your website and while files they have accessed. The IP address that coresponds to the files edited, you can then block using the plugin I mentioned before. Joomla 2.5 is very hard to hack so it is rather likely you have an extension that is badly developed and allows SQL injection. Therefore you should always choose popular extensions to install on your website when they are database related.
Hope this helps you in the future. Regards
EDIT : You can also password protect your folders in the FTP for additional security.
You may also find this extension quite useful
After you recover from this, make sure you place a password on the /administrator directory with .htaccess, assuming this is a Linux based server.
Couple of steps that will help you identify the point of access.
Also depends on if you have access to some server side tools.
Contact host and ask them if they run Mod_Sec if so ask them for the Mod_sec flag for that IP.
Ask the host if they run any type of maldet tools - if so ask for a scan of your account.
If you have shell access run a check on what were the most recent files changes... Side from tmp and cache files.
Fixing the hack
1. Change all your passwords -
2. Install project honey pot.
3. Admin tools install is good but you need the pro version to really gain access to the security tools.
4. Migrate to a host that specializes in Joomla platforms, in most cases they already have the accounts configured for common security issues in Joomla.
Getting hacked really sucks... Good luck!
Relocate your administrator page by editing the config.php files .. and edit your FTP permission settings. If your administration login url was the standard location. (www.site.com/administrator ) change this location and block access using your hosting control panel to only certain ip address (and even restrict access by hours of availability.
How many administrator user accounts do you have. There really should be only one person with super user access . It is really not productive or safe to have other users that do minor edits of the website with administrator privileges; and they could accidentally cause issues. These are basic steps and there is a lot more you can do. Send an email if you need help/step by step instructions. Hope all goes well.
I have ColdFusion Builder 2.0.0 installed and I am trying to look at the much vaunted step debugging. However, I cannot seem to get it to work as I don't have my site / JRun install setup in the naive way the examples show.
I am using version 9,0,1,274733 of ColdFusion and my configuration is as follows:-
Installed as multi-server version with Jrun here:- c:\Apps\JRun4
application files are here:- d:\websites\my.website.com
web root is here d:\websites\my.website.com\www
core library of CFCs is here d:\websites\frameworks\core which is mapped in CF as core
I have read this watched this http://help.adobe.com/en_US/ColdFusionBuilder/Using/WS0ef8c004658c1089-31c11ef1121cdfd6aa0-7fff.html and this http://forta.com/blog/index.cfm/2007/5/30/CF8-Debugger-Getting-Started and watched this https://experts.adobeconnect.com/_a204547676/p33029638/?launcher=false&fcsContent=true&pbMode=normal but I get stuck at the point after you have configured RDS and you are setting up the server for your project.
Now I am pretty sure the above is correct, when I move to the next page in the wizard I get the following:-
Now I as I understand it my Server Home should be c:\Apps\JRun4 and my Document root should be d:\websites\my.website.com
This all looks like it is going to be fine until you actually try and debug when I get
followed by
I can confirm that the server is running and RDS is enabled as in the RDS Dataview I can see all my databases.
Any help would be gratefully received as this is very frustrating and the documentation is very lacking.
There is a video tutorial as well that you may want to check and see if that helps. http://blogs.adobe.com/anand/2011/01/learn-how-to-debug-coldfusion-applications-using-coldfusion-builder-2.html
You need to specify the RDS username/password and the "application server name". If you are using the base instance that was installed when you setup the multiserver install of CF that is "cfusion", otherwise its the name of the instance you are using.
The RDS username is most likely "admin" unless you setup custom users for RDS. The password is the RDS password you specified when you installed CF.
I tried and installed the JA Blazes quick start template (which includes all the modules and extensions, as shown in their live demo) for Joomla 1.5 on my local server and all worked perfectly well, but when I installed it on my domain server, the install sample data fails. I do see the DB being updated, but the installation just never ends. The installation of sample data goes on forever. Is there a way I can figure out if something went/is-going wrong ?
Thanks in advance..
Sounds to me like the connection with the db server is timing out.
If you can work out where the sql files are stored within the distribution (usually /installation/sql/ ) you could insert the sql manually using phpMyAdmin or from the command line.
If the demo installed fine on your local machine there is no need to 'install' it at all on the remote server.
FTP all of the files up to the server.
Use phpMyAdmin locally to export the database
Use phpMyAdmin on the remote server to import the backed up sql.
Finally edit the configuration.php file with the database details and paths for the remote server.
A final alternative would be to utilise Akeeba Backup or similar to package up the site and move it from local to remote. This is a fantastic tool that works around most memory limits and other annoyances on shared hosting.