I use imagerizer on my website which works very well. I purchased a license for my domain like fotoapparatuur.nl and installed it in the webconfig assuming this would work on all subdomains as described on the licensing page. However I actually use it on www.fotoapparatuur.nl and get red dots on my pictures.
The resizer.debug states:
resizer configuration(Error): No license found for domain www.fotoapparatuur.nl - features installed: R4Performance or R4BlobProviders AND R4Performance or R4DiskCache AND R4Creative or R4Watermark
List of installed domain licenses:
fotoapparatuur.nl => R4Performance
How do I get imageresizer to work on subdomains?
You are using the Creative edition, but only bought a Performance license. Uninstall the Waterkmark plugin (Creative edition) and licensing system will be happy.
Related
Windows 10 has a feature to block any font outside the %windir%/Fonts directory from loading in a browser.
Our entire website (AEM + Apache webserver) uses a proprietary purchased font which is hence blocked in all PC's. Is there any way to bypass this setting so that the font loads seamlessly in all users.
We need to do something from AEM/Apache websrver/Akamai CDN end because any local changes will not be possible for end users to follow.
I didn't find much help online for this.
The documentation says - "By default, this feature is not turned on." so i would assume you are facing issues on company issued laptops that have this security feature enabled.
Depending on your fonts licensing you could choose to do following -
Use user-agent information to detect if the OS is windows 10
If Windows 10 is detected show an overlay with the link to download and install fonts
To let the font work with this setting, it is to install the font on each machine with the Untrusted font setting turned on and then declare the font with a fallback.
The second option would it be to whitelist the application, in this case, the browser to be whitelisted as explained in the Microsoft website here: https://technet.microsoft.com/en-us/itpro/windows/keep-secure/block-untrusted-fonts-in-enterprise
I had a similar issue, with Icomoon, but the concepts would be the same one: install the font in the system and then declare a fallback font.
This might help you in the process:
http://maurizionapoleoni.com/blog/how-to-display-fontawesome-icomoon-and-font-icons-on-a-windows-10-with-blocked-untrusted-fonts/
I'd like to give my users a shrinked package of Xampp (without MySQL and tomcat folders). That means that I'd like to take the original ZIP file (from sourceforge.net) and remove some unnecessary folders (but leave Apache folder since I need its web server). Am I allowed to do so? Am I allowed to give my users such an distribution kit?
Thanks
XAMPP is a very easy to install Apache Distribution for Linux,
Solaris, Windows, and Mac OS X. The package includes the Apache web
server, MySQL, PHP, Perl, a FTP server and phpMyAdmin.
Nothing is owned by the creators of the XAMPP installer, so the simple answer is: Yes, you can download and remove content from the .zip file and serve that.
Visit their homepage for further information.
XAMPP is published under GNU License, so you can basically modify XAMPP the way you want to, and then you need to publish it under GNU as well.
Is there a way to manage images uploaded into a plone system, but have them be synced and automatically served with Amazon S3/Cloudfront?
I've seen reference to a project that doesn't look like it's been touched since early 2011: http://plone.org/products/collective.cdn.core/ and that only has experimental image support, and not necessarily for Amazon s3/cloudfront
There is not yet an add-on product that makes this "point-and-click" easy. https://github.com/collective/collective.cdn.core suggest that collective.cdn.core has continued to be developed, although the authors haven't pushed their releases to plone.org (shame shame!). It still does not appear to include "native" Amazon/CloudFront support, but I suspect the add-on authors would welcome either code contributions or sponsorship to add that end.
I have a live site running on cPanel. I would like to write some WHM plugins to extend WHM functionality. But the problem I am facing is I don't seem to find a way to get cPanel as a developer version - which I can run on a development environment, test it and then install it to production.
Any idea anyone?
There isn't a developer cPanel available, you could try having a test server/environment with cPanel installed, making the plugin etc and just testing live on that.
you could always open a support ticket with cPanel and see what the have to offer, they might have something which would work for you, but just isn't publicly displayed as such.
I have developed an extension to Magento Community edition.
I would like to test it on the Enterprise edition.
How can I do that?
Do you think there will be changes between those versions code-wise?
Thanks
I use EE daily. All the differences I can detect are in the form of extra modules in "app/code/core/Enterprise", class names start with "Enterprise" instead of "Mage", some are encoded with ionCube. There is an "enterprise" theme too but it is very similar to "modern". The rest of Magento is the same as the Community Edition so your extension will likely work on both equally.
However you cannot claim compatibility without testing it, that would be irresponsible. It is possible you have overridden something which is then later re-overridden by the other edition. You probably don't want to buy a years licence just for that so you'll have to ask for volunteers, the best places are Magento's forum and chat. Failing that you could advertise on one of the many freelance programmer sites for someone who is in a position to help, that will be cheaper than a whole copy of EE.
Lastly there is the issue of registering on Magento Connect. So far only aheadWorks have the privilege of appearing in the "Enterprise Ed." section. (The "Professional Ed." section isn't even active yet.) You may not get a chance to list your extension there although you can always explain the salient parts on your own website.
Magento Enterprise edition differs from Community edition by following items:
1) There are additional modules, that complement Mage modules. They all have Enterprise namespace (Enterprise_ prefix instead of Mage_ prefix). Enterprise modules either add some new functionality, or modifiy behaviour of Mage modules.
2) Enterprise has its own design scheme. About 30% of templates are overriden, others fall back to base/default theme
3) Enterprise has different license
So, reviewing mentioned above, you cannot guarantee stable work of your CE extension without testing it on EE. It's very probable that your module will fork fine, but I'd estimate a 10% probability that your extension requires some fixes to work normally with EE.
Strictly speaking, you can test your extension only having your own Magento EE ($10 000+).
However there's the other way. Magento EE license allows the buyer to give access to his Magento EE version to people, that are developing some functionality for buyer's Magento. So you can sell your extension to someone having Magento EE, notifying him, that it was not tested on EE and you need to do it. Your client will give you access to his Magento EE and you'll be able to test and debug the extension. That conforms Magento EE license, because you'll be a hired developer for Magento EE owner and you'll be developing extension for his Magento EE.
Of course you should notice that your account at Magento Connect must have special access to posting EE-extensions - usual account can not do this. You need to ask Magento support how to get such privilege.
From my own opinion I recommend do not bother with EE functionality, as it's not easy to perform whole process of testing and posting it as EE extension. CE market is wider (although not so money-full), so you can sell it here.
I agree with clockworkgeek that you are likely not to have any problems, but also that there are overrides in Magento EE that you need to be aware of. Please do find an EE installation to check on, as there may be changes.
I have developed a magento module. It works fine for community edition and enterprise edition in my local environment. After installed it in the live site it works fine for community edition, but not for enterprise edition. It is not showing any admin configuration in enterprise edition. Am I missing anything?