quarta-feira, setembro 30, 2015

Conversor de texto em áudio (mp3)

Soar | Conversor de texto em áudio (mp3)



Converta seu Texto em Áudio.

Conversor de texto em mp3
at Nenhum comentário:

quinta-feira, setembro 24, 2015

Root galaxy s6 deep sleep problem fix


Another threads

http://forum.xda-developers.com/galaxy-s6/general/battery-drain-root-twrp-to-fix-t3088860
http://forum.xda-developers.com/showpost.php?p=60383471&postcount=49

EDIT: HomerSp posted a TWRP-flashable ZIP here:http://forum.xda-developers.com/show...7&postcount=56

It still requires you are rooted with SuperSU though. If not, flashing back stock kernel and stock recovery with ODIN will still fix the deep sleep issue.

---

If using SuperSU, copy/paste this into an ADB shell, it'll reboot your device, and the problem will be fixed. You might need to grant permissions on-screen after the first line.

Code:

su mount -o rw,remount /system /system mkdir /system/su.d chmod 0700 /system/su.d echo "#!/tmp-mksh/tmp-mksh" > /system/su.d/000000deepsleep echo "echo 'temporary none' > /sys/class/scsi_disk/0:0:0:1/cache_type" >> /system/su.d/000000deepsleep echo "echo 'temporary none' > /sys/class/scsi_disk/0:0:0:2/cache_type" >> /system/su.d/000000deepsleep chmod 0700 /system/su.d/000000deepsleep reboot

This takes @HomerSp 's fix listed a few posts up, and has SuperSU apply it on every boot.

at Nenhum comentário:

quarta-feira, setembro 23, 2015

Creating a Magento Multi-Website - a Multi Store Checklist

Creating a Magento Multi-Website - a Multi Store Checklist | Eddie May



Magento Multi-Website Checklist

One of Magento’s great features is the multi-site & multi-store capabilities. If you’re new to Magento, this means that you can run more than one website from the same Magento installation. Having just added yet another website to a client’s Magento installation, I thought I’d jot the steps down as an aide-mémoire. So below I’m going to outline a checklist of the actions required to set up a mutli-website store in Magento.
For the purposes of the this example, assume I already have a Mage website eddiemay.me.uk and want to add another website eddie-may.com. Also assume that I’m selling to the same country with the same Tax & shipping rules, payment gateway, etc. Also assume that I’m going to be using the same template but use a different skin to make it look different.
NB: This example is for Magento Community Edition 1.7.0.2 – earlier editions had different ways of routing requests using .htaccess or index.php.
  1. Buy a multi-domain SSL certificate. Make sure that new domain is associated with this certificate.
  2. Point your new domain name at your server.
  3. Log into Magento and do a backup – peace of mind, etc.
  4. Set up a new root category & then add any sub categories as required. This root category is going to be ‘home’ of the new website.
  5. Go to System/Manage Stores. Next, hit the Create Website button & fill in the necessary information – keep a note of the value you put in the “code” field. In my example I’m going to use “may” as the code value.
  6. Repeat the steps for Create Store & Create Store View. When you create a store you set the root category to be the one you’ve just created in step 4 above.
  7. Go to CMS/Pages and create a new home page & associate it with the new Website.
  8. Now go to System/Configuration and change the ‘Current Configuration Scope’ to your new website. You’ll notice that the values are a copy of the default website. You’re now going to have to go through a number of tabs and change the required values. Here I’ll refer only to the essential changes.
  9. Under System/Configuration/Web change the Secure & Unsecure urls to your new domain name – in this case eddie-may.com. Also under Default Pages set the CMS Home Page to the page you created in step 7. Under the Session Cookie Management tab, add your new domain as the Cookie Domain like so -> .eddie-may.com
  10. In the Design tab you now have a choice of determining how the website will look. Here I’m going to assume that you’ll use the same template but use CSS to change the style of the site.
  11. So, upload a new skin under the /skin/frontend/default. Lets assume the new skin is called eddiemay, that means you’ll have a folder like so /skin/frontend/default/eddiemay
  12. If that’s the case, the design settings will be Package = default; Skin (Images/CSS) = eddiemay; Layout & Default will be the same values as your first website.
  13. Still under the Design tab, change the HTML Head, Header, Footer, etc as required. From an SEO perspective, make sure that the Default Title & Description are unique.
  14. Now go to Store Emails – you’ll need to change email addresses to reflect the new domain name. Make sure that these email accounts actually exist before going live.
  15. Under Contacts change the main contact email as required.
  16. Under Sales/Invoice & Packing Slip Design – change the default logos to your new logo.
  17. Under Sales/Sales Emails – you may have to change the email templates if you’ve heavily customised your default email templates (you may have hardcoded your store name, for example).
  18. That’s more or less it for the System/Configuration settings.
  19. Now go to CMS section. Here you may have to create new CMS pages & Static Blocks, or at least associate existing ones with the new website. At a minimum you’ll need to associate the Contact, About, Privacy, Terms, Shipping pages with the new website.
  20. The next thing you’ll need to do is add the new website to your .htaccess file. You need to add the new domain like so:
  22. ## multidomain
SetEnvIf Host www\.eddiemay\.me.uk MAGE_RUN_CODE=base
SetEnvIf Host www\.eddiemay\.me.uk MAGE_RUN_TYPE=website
SetEnvIf Host ^eddiemay\.me.uk MAGE_RUN_CODE=base
SetEnvIf Host ^eddiemay\.me.uk MAGE_RUN_TYPE=website
    SetEnvIf Host www\.eddie-may\.com MAGE_RUN_CODE=may
SetEnvIf Host www\.eddie-may\.com MAGE_RUN_TYPE=website
SetEnvIf Host ^eddie-may\.com MAGE_RUN_CODE=may
SetEnvIf Host ^eddie-may\.com MAGE_RUN_TYPE=website
  23. You’ll notice that I’ve used the code “may” – this was the value I entered in the new Website code field in step 5 above.
  24. Upload the new .htaccess file.
  25. Now test your new website – chances are that you’ll get an error. Downloading the error report will give a cryptic “SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘database-name.catalog_category_flat_store_3′” doesn’t exist – or something similar. If this happens, log into your Magento administration UI, go to System/Index Management & you’ll probably see that several indexes need re-indexing. Once complete, your website should now work as expected.
  26. If all is good, its now time to add some products. You could copy products over from the original website but personally I’d create them from scratch or upload new ones. This is because you can then optimise their descriptions, etc., to avoid duplicate content penalties, etc.
Well, I think that covers all the bases. This will probably take you about 2 hours to complete, depending on the amount of customising of Email template, Static Blocks, etc. The CSS customisations are another thing altogether.
If I’ve left anything out, please let me know. Either way, I hope you find it useful.
at Nenhum comentário:

Digging for hosts on FreeBSD 10 | The FreeBSD Forums

Digging for hosts on FreeBSD 10 | The FreeBSD Forums



Digging for hosts on FreeBSD 10

FreeBSD 10 now has unbound for DNS lookups, which is actually a lot better than BIND (the zone server, nsd, is not in FreeBSD base), but I was confused when my favourite DNS tooldig(1) was MIA. So, what can we use now?

host(1)

host(1) is usually part of BIND, but for FreeBSD 10 a compatible replacement has been imported from ldns-host.

Code:
[~]% host arp242.net
arp242.net has address 66.111.4.53
arp242.net mail is handled by 20 in2-smtp.messagingengine.com.
arp242.net mail is handled by 10 in1-smtp.messagingengine.com.


It has a nice short output, which is cool. For a reverse lookup, just use the IP address:

Code:
[~]% host 66.111.4.53
53.4.111.66.in-addr.arpa domain name pointer web.messagingengine.com.


Using dig arp242.net NS

Code:
[~]% host -tNS arp242.net
arp242.net name server ns0.transip.net.
arp242.net name server ns2.transip.eu.
arp242.net name server ns1.transip.nl.


dig arp242.net ANY can be done with host -a

Code:
[~]% host -a arp242.net

Trying "arp242.net"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24937
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 3

;; QUESTION SECTION:
;arp242.net.                    IN      ANY

;; ANSWER SECTION:
arp242.net.             56930   IN      NS      ns0.transip.net.
arp242.net.             56930   IN      NS      ns2.transip.eu.
arp242.net.             56930   IN      NS      ns1.transip.nl.

;; ADDITIONAL SECTION:
ns2.transip.eu.         85989   IN      A       217.115.203.194
ns1.transip.nl.         7146    IN      A       80.69.69.69
ns0.transip.net.        86172   IN      A       80.69.67.67

Received 158 bytes from 192.168.178.1#53 in 0 ms


drill(1)

drill(1) comes with Unbound, and behaves a bit more like dig.

Code:
[~]% drill arp242.net
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 33602
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; arp242.net.  IN      A

;; ANSWER SECTION:
arp242.net.     86326   IN      A       66.111.4.53

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 0 msec
;; SERVER: 192.168.178.1
;; WHEN: Tue Mar  4 21:27:18 2014
;; MSG SIZE  rcvd: 44


Reverse lookup with -x:

Code:
[~]% drill -x 66.111.4.53
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 19910
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; 53.4.111.66.in-addr.arpa.    IN      PTR

;; ANSWER SECTION:
53.4.111.66.in-addr.arpa.       526     IN      PTR     web.messagingengine.com.

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 0 msec
;; SERVER: 192.168.178.1
;; WHEN: Tue Mar  4 21:28:04 2014
;; MSG SIZE  rcvd: 79


And classes work like dig as well.

Code:
[~]% drill arp242.net ANY
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 62701
;; flags: qr tc rd ra ; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; arp242.net.  IN      ANY

;; ANSWER SECTION:
arp242.net.     86177   IN      A       66.111.4.53
arp242.net.     86177   IN      RRSIG   A 7 2 86400 20140807142905
20140205142905 3707 arp242.net.
JWyPfrgV+sauV03/8eKSAzzM+GIRLLcqzye1BKFYsYwoAOxS+yBQNOzoSSJiuWMGj+zhvu1hyK0E3yFgSyWbzITTdigkWBwnkrVLOEnZ/CRVwj68/9MhLC/l2w7YyOyAkty2EVOWZljduVo1NIajB593JIWpDVbh0rKwn1X7IOY=
arp242.net.     86177   IN      MX      20 in2-smtp.messagingengine.com.
arp242.net.     86177   IN      MX      10 in1-smtp.messagingengine.com.
arp242.net.     86177   IN      RRSIG   MX 7 2 86400 20140807142905
20140205142905 3707 arp242.net.
MvvwO7HNnvJXOazXTbGtk28ofhPttYdiF5enHcAREs7ZevQP2k8hVF6xXZSPLScDCPP1R4CPaZrq7XtUPkWDqPSjD3zcBaIE8VyKZIPmAotR7ZpGIlmVDEdqcHlvbFZF9HWZM4wwSe8hO97sy3KRaqR3GxE167n6D0njw8B5PSY=

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 1154 msec
;; SERVER: 192.168.178.1
;; WHEN: Tue Mar  4 21:29:47 2014
;; MSG SIZE  rcvd: 453

;; WARNING: The answer packet was truncated; you might want to
;; query again with TCP (-t argument), or EDNS0 (-b for buffer size)


+short doesn’t seem to work, though

Code:
[~]% drill arp242.net +short
;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN, id: 609
;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 
;; QUESTION SECTION:
;; +short.      IN      A

;; ANSWER SECTION:

;; AUTHORITY SECTION:
.       815     IN      SOA     a.root-servers.net. nstld.verisign-grs.com.
2014030401 1800 900 604800 86400

;; ADDITIONAL SECTION:

;; Query time: 0 msec
;; SERVER: 192.168.178.1
;; WHEN: Tue Mar  4 21:29:52 2014
;; MSG SIZE  rcvd: 99

at Nenhum comentário:

terça-feira, setembro 22, 2015

FlashFire is the spiritual successor to Mobile ODIN

[Android 4.2+][ROOT] FlashFire - Play BETA - PREVIEW - XDA Forums



http://flashfireapk.com/

MobileOdin

It's long overdue for release, but some i's still need to be dotted and some t's crossed. That being said, most of the functionality actually works well already, and it's pretty darned powerful. I have used it to update various Samsung devices from 4.x to 5.x, done (block-level!) OTAs on Nexus devices, etc.

If you're fairly tech-savvy and/or used to Mobile ODIN I suspect you won't have much trouble getting around with this app. Updates and the manual (which would be bloody useful, wouldn't it?) are coming over the next few days and weeks.

Notes and hints to help you use it:
- No kernels or recoveries are flashed for FlashFire to run, Android is torn down and restarted in a minimalist manner for the flashing part of the app to run. I'm sure this will completely fail on some devices.
- A lot(!) of memory is used, likely the entire operation will fail on low-memory devices. I strongly suggest you make an 'ID' backup as the very first test and see if that works at all.
- Technically it should be compatible with 4.2, but note virtually all of the testing so far has been done on 4.4 and 5.0 firmwares.
- SuperSU is required, unless you are running a CM-based ROM
- While development has focused so far on Samsung and Nexus compatibility and features, it should be able to function on many devices. Specific support for some other manufacturers is coming via updates soon.
- Individual files need to be named correctly (after their partitions) to be flashable or be contained in archives. Archive-wise, TAR and ZIP are supported. Compression-wise, ZIP, GZIP and BZIP2 are supported. These can be embedded inside each-other, so yes, you can directly flash the standard ZIP-inside-TGZ Nexus firmwares, as well as TAR-inside-ZIP Samsung firmwares. More formats are to come.
- Backups can be to internal, external (sd) or USB storage. The backups are compressed. There is no way of knowing if the backup will fit, you are not warned about this.
- Backups are standard TGZ's for file-based, and plain GZIP'd for raw partitions
- For block-level OTAs, flash a stock system partition or restore a (raw!) system (and vendor) backup before applying the OTA. After the OTA action, create a (raw!) backup of system (and vendor). The latter will be restorable to apply the next OTA.
- The embedded SuperSU version installed by EverRoot is v2.49 BETA

- Pro version is unlocked if you have Mobile ODIN Pro installed, but you still see an upgrade option. This is a (much cheaper) In-App Purchase you can optionally do, so you don't need to keep MOP installed.
- Pro version actually does nothing different at the moment.

In case of issues, immediately after rebooting back into Android:
- Post /sdcard/FlashFire/lastlog
- Post /proc/last_kmsg
The latter may not be present, and is replaced on every reboot. So if you rebooted twice, no sense posting it.

If you are reading to start messing around with it, this is how you get the BETA:
- Join the G+ community using the same Google account as you're using for Play on your phone/tablet here:https://plus.google.com/communities/...25291346007584
- Sign up to receive the BETA versions from Play here: https://play.google.com/apps/testing/eu.chainfire.flash
- Use the link provided after sign-up to download the app. Note that it may take minutes to even hours before the provided link actually works.

If you have no idea what any of the above means, you might want to wait with playing with this until proper instructions are available, and more people have tested it.
at Nenhum comentário:

sexta-feira, setembro 11, 2015

How To Setup Multiple Magento Stores

How To Setup Multiple Magento Stores — Crucial Web Hosting

alternative link and instructions
https://www.properhost.com/support/kb/30/How-To-Setup-Magento-With-Multiple-Stores-And-Domains


very nice.

you must have to make things easier the domains pointing to the same DOCUMENT_ROOT

then change index.php



There are numerous ways to setup multiple Magento stores that all share the same codebase and backend, but what method you use depends on your needs.
This article is written with cPanel in mind, though the methodologies listed below apply no matter what control panel you're using. You will need Magento 1.4.x or greater installed too.

Jump To Section

  1. URL Structure
  2. Shared Hosting Caveat
  3. Adding Another Store In Magento
  4. Parked Domain Method
  5. Addon Domain Method
  6. Sub Domain Method
  7. Subdirectory Method
  8. Managing Multiple Stores
  9. Secure Checkout For Each Domain

URL Structure

The actual URL structure of your stores is a matter of personal preference. You can, for example, have two entirely different stores running on the same domain that share the same instance of Magento:
  • mall.com/shoes
  • mall.com/shirts
These stores could also be setup on their own domain and still share the same instance of Magento:
  • shoes.com
  • shirts.com
Another example would be a mall type setup, where your primary domain is the portal to access various stores:
  • mall.com
  • shoes.mall.com
  • shirts.mall.com
Regardless of the URL structure, the method for setting this up will pretty much be the same, and the result is what we're really after, which is to have one codebase for all of your stores, and one backend to manage all of these stores from.

Shared Hosting Caveat

If you want each store to have it's own SSL certificate and don't want to share a single checkout, e.g. you don't want visitors leaving domainA.com to checkout on domainB.com, then you will not be able to do this in a shared hosting environment.
The reason why you cannot do this is simple. In order for a website to have an SSL certificate, it requires a dedicated IP address.
There's no way to allow an addon or parked domain in cPanel to have its own IP address. Instead, it shares the IP address of the primary domain.
You probably think you could sign up for two shared hosting accounts, so each one has its own dedicated IP address, but that won't work either.
Since it's shared hosting, there are security measures in place to prevent one user from reading the files of another user.
So for shared hosting clients, you're limited to the following scenarios:
  1. All of your stores do not have a secure checkout, which is fine if you're using PayPal, Google Checkout, or a similar third-party service that handles the processing of card data on their website. For example, visitors to any of your stores are redirected to a third-party website for card processing.
  2. All of your stores are setup as sub domains, and you've purchased a wildcard SSL certificate.
If you do need an SSL certificate for all of your domains, you will need to be in a dedicated hosting environment, such as our Split-Dedicated platform. In this type of environment, we can install a multi-domain or UCC certificate.

Adding Another Store In Magento

The first thing we need to do is setup our second store in Magento.
We're going to do a hypothetical here for the naming conventions, and assume we own shirts.com. Adjust the values accordingly for your own store.
  1. Login to the Magento admin.
  2. Go to the Catalog tab, and select Manage Categories.
  3. Click on the Add Root Category button on the left.
  4. On the right, for the Name, we'll enter Shoes.com. Set the dropdown to Yes for both Is Active and Is Anchor.
  5. Click the Save Category button.
  6. Go to the System tab and select Manage Stores.
  7. Click on the Create Website button.
  8. For the Name, we'll enter Shoes.com, and for the Code, we'll enter shoes. We'll use this value later, so don't forget this!
  9. Click the Save Website button.
  10. Click on the Create Store button.
  11. For the Website, select Shoes.com from the dropdown. For the Name, we'll enter Main Store. For the Root Category, select the Shoes.com from the dropdown.
  12. Click on the Save Store button.
  13. Click on the Create Store View button.
  14. For the Store, select Main Store from the dropdown, making sure it's for the Shoes.com website. For theName, we'll enter English. For the Code, we'll enter shoes_en. For the Status, select Enabled from the dropdown.
  15. Click the Save Store View button.
  16. Go to the System tab and select Configuration.
  17. For the Current Configuration Scope (located on the top left), change the dropdown menu from Default Config to Shoes.com.
  18. Select Web from the sidebar on the left under the General heading.
  19. For both the Unsecure and Secure sections, uncheck the Use default box next to the Base URL item, and enter the URL for your store, e.g. http://www.shoes.com/. Don't forget the trailing slash!
  20. Click the Save Config button.
Now that we have our second store setup, you'll need to choose one of the following methods for actually setting up the store on the server-side so visitors can access it.
If the URL structure you've chosen will have different domains for each store, the parked domain method is the fastest and easiest method.

Parked Domain Method

For this method, we'll pretend we own shirts.com and shoes.com. The shirts.com domain is our primary domain, and Magento is already installed on it. Here's how we would set this up for the shoes.com domain:
  1. Login to cPanel for your domain and click on the Parked Domains icon.
  2. In the input field, enter the domain name that you'll be setting up as a second store, e.g. shoes.com.
  3. Click on the Add Domain button.
  4. Open up the index.php file for Magento and look for this line (it's the last line of the file):
    Mage::run($mageRunCode, $mageRunType);
    …and right before this, we're going to add the following code:
    switch($_SERVER['HTTP_HOST']) {
    case 'shoes.com':
    case 'www.shoes.com':
        $mageRunCode = 'shoes';
        $mageRunType = 'website';
    break;
}
    If you have more than two stores, you will need to add additional cases to the above code block, e.g.:
    switch($_SERVER['HTTP_HOST']) {
    case 'shoes.com':
    case 'www.shoes.com':
        $mageRunCode = 'shoes';
        $mageRunType = 'website';
    break;
    case 'hats.com':
    case 'www.hats.com':
        $mageRunCode = 'hats';
        $mageRunType = 'website';
    break;
}

Addon Domain Method

This is the same scenario as above, except it takes a little longer to setup. This method might be more useful to you if, for example, you wanted to have a blog on one domain, but not on the other. You couldn't do that with a parked domain. Here's how we would set this up for the shoes.com domain:
  1. Login to cPanel for your domain, and click on the Addon Domains icon.
  2. For the New Domain Name, we'll enter shoes.com. cPanel will automatically fill in the next two fields, so remove public_html/ from the Document Root field, leaving us with just shoes.com. This step isn't required, but for organizational purposes, it makes more sense.
  3. Set a password for this domain and click on the Add Domain button.
  4. Login to your site via SSH, and go to the directory that we previously set in the Document Root field above when adding our domain. In our case, we would do the following:
    cd shoes.com/
  5. Copy the index.php and .htaccess file from the directory where Magento is installed, which would be in our root web directory:
    cp ../public_html/index.php ../public_html/.htaccess .
  6. Open up the index.php file and look for this line (it's the last line of the file):
    Mage::run($mageRunCode, $mageRunType);
    …and right before this, we're going to add the following code:
    $mageRunCode = 'shoes';
$mageRunType = 'website';
  7. Lastly, we need to create symbolic links to point to a few directories:
    ln -s ../public_html/app ./app
ln -s ../public_html/errors ./errors
ln -s ../public_html/includes ./includes
ln -s ../public_html/js ./js
ln -s ../public_html/lib ./lib
ln -s ../public_html/media ./media
ln -s ../public_html/skin ./skin
ln -s ../public_html/var ./var

Sub Domain Method

For this method, we'll pretend we own mall.com, and it's setup as a portal that links to the various shops within the mall. Magento will be installed on the mall.com domain, and all of the shops will be in sub domains, e.g.:
  • shoes.mall.com
  • shirts.mall.com
Here's how we would set this up for the shoes sub domain:
  1. Login to cPanel for your domain, and click on the Sub Domains icon.
  2. For the Sub Domain, we'll enter shoes. cPanel will automatically fill in the next field, so removepublic_html/ from the Document Root field, leaving us with just shoes. This step isn't required, but for organizational purposes, it makes more sense.
  3. Click the Create button.
  4. Login to your site via SSH, and go to the directory that we previously set in the Document Root field above when creating our sub domain. In our case, we would do the following:
    cd shoes/
  5. Copy the index.php and .htaccess file from the directory where Magento is installed, which would be in our root web directory:
    cp ../public_html/index.php ../public_html/.htaccess .
  6. Open up the index.php file and look for this line (it's the last line of the file):
    Mage::run($mageRunCode, $mageRunType);
    …and right before this, we're going to add the following code:
    $mageRunCode = 'shoes';
$mageRunType = 'website';
  7. Lastly, we need to create symbolic links to point to a few directories:
    ln -s ../public_html/app ./app
ln -s ../public_html/errors ./errors
ln -s ../public_html/includes ./includes
ln -s ../public_html/js ./js
ln -s ../public_html/lib ./lib
ln -s ../public_html/media ./media
ln -s ../public_html/skin ./skin
ln -s ../public_html/var ./var

Subdirectory Method

This is the same scenario as above, except all of the shops will be in subdirectories, e.g.:
  • mall.com/shoes
  • mall.com/shirts
Here's how we would set this up for the shoes subdirectory:
  1. Login to your site via SSH, and create a subdirectory where your second store will be:
    cd public_html
mkdir shoes/
cd shoes/
  2. Copy the index.php and .htaccess file from the directory where Magento is installed, which would be in our root web directory:
    cp ../public_html/index.php ../public_html/.htaccess .
  3. Open up the index.php file and look for this line (it's the last line of the file):
    Mage::run($mageRunCode, $mageRunType);
    …and right before this, we're going to add the following code:
    $mageRunCode = 'shoes';
$mageRunType = 'website';

Managing Multiple Stores

It's very important to remember that now that you have multiple stores to manage from one admin panel, that you make sure you're changing the configuration for the appropriate store.
In the System → Configuration section, if you leave the dropdown menu for Current Configuration Scope set to Default Config, it will globally change the values for all of your stores, assuming you haven't removed the checkmark next to Use default throughout the configuration sections.
You can change the configuration values globally, for each website, and for individual store views.

Secure Checkout For Each Store

For those of you in dedicated hosting environments, you can follow either the addon or parked domain method from above, and edit the httpd.conf file to give the addon or parked domain a dedicated IP address. However, this is not advised. Your changes will most likely be overwritten with a control panel upgrade, Apache or PHP rebuild, or even simple maintenance.
Your best bet would be to purchase a Unified Communications Certificate (UCC), also known as a multi-domain or multiple domain certificate. If you're on our Split-Dedicated product, after you've purchased and installed this certificate, we can make the necessary changes to support this type of certificate (this is something we have to do, since it's not natively supported by cPanel). Once we have the SSL setup, you simply follow the parked domain method for each domain you've assigned to your UCC certificate.
This is just one of the many advantages of running your online business in a more secure and flexible hosting environment like this.
Once you've done the above, all of your stores will have their own secure checkout and will still share the same codebase and backend for management purposes.
at Nenhum comentário:

Error while adding an Addon domain in cPanel.

Error while adding an Addon domain in cPanel. | CryBit





Detailed error message:

Error:Using nameservers with the following IPs: xxx.4x3.xx9.2x,6x.xx8.xx9.1xx Sorry, the domain is already pointed to an IP address that does not appear to use DNS servers associated with this server. Please transfer the domain to this servers nameservers or have your administrator add one of its nameservers to /etc/ips.remotedns and make the proper A entries on that remote nameserver.
Selection_119
Solution:

You can simply solve this error from your WHM panel. There is an option called “Allow Remote Domains” in WHM tweak settings. Switch ON the option “Allow Remote Domains” to add new Addon domains that having name servers other than your server. Follow these steps to enable it.

Do follow these steps:

Login to WHM >> Home >> Server Configuration >> Tweak Settings >> Find "Allow Remote Domains" option under Domain group and turn ON it >> then SAVE.
Selection_120

###Please See###

(Note :Allow creation of parked/addon domains that resolve to other servers (e.g. domain transfers) This can be a major security problem. If you must have it enabled, be sure not to allow users to park common Internet domains.Please make sure that this option is turned OFF after adding Addon domain.)
Hope this steps help you!
at Nenhum comentário:
Assinar: Postagens (Atom)