In this wiki that I recently set up, the images are not displayed. I tried both local uploads and InstantCommons (like I did in the main page), but the result is the same. The software is 1.16.5 and I cannot upgrade it since the hosting server only supports a PHP compatible to this MediaWiki version at the best. Any suggestion?
Danilo's own answer: I solved the problem. My LocalSettings.php was missing:
$wgUploadPath = "$wgScriptPath/uploads";
$wgUploadDirectory = "$IP/uploads";
which were needed to allow independent creations of URL.
Related
I have installed my theme in C:\xampp\htdocs\projects\c5\surreymarketingpr_gmk\packages\dotawesome_warm\themes\dotawesome
its working fine on localhost but not on live site. Also its an older version of concrete5 because this theme is not compatible with the latest versions of concrete5.
You aren't really giving enough information here. Not working is not very helpful. What do your error logs contain? What's the website URL?
There are several things that can impact uploading to an online host, such as PHP version, MySQL version, .htaccess settings, file permissions, etc.
Another very possible problem is that you didn't have this in your my.ini under XAMPP when you installed concret5:
lower_case_table_names=1
If you'd like help with this you can contact me jasteele12 at concrete5.org
There's two directories in the Github respositories:
magmi
magmi-0.8
Which one should I use?
I had this question as well. After sniffing around, it looks like the magmi-0.8 folder may be reserved for the future releases of Magmi 0.8. The current stable is 0.7.19
I tried to run the magmi-0.8 version but got a bunch of errors, so I am now running the app from the base magmi folder. Fingers crossed this version plays nicely with Magento CE 1.8
This post provides more info:
https://github.com/dweeves/magmi-git/issues/12
This is not something standard for GitHub.
You're rather referring to Magento Mass Importer project hosted on GitHub.
As you're starting now, you should use the magmi directory, as it has the most updated code.
I have created a PDF from several web pages using wkhtmltopdf.
Is there a way to link across pages, for example from page 10 to 15.
I tried creating an element with an ID and then an anchor to link to it, but this does not work within the same page or across pages. It turns the link into an absolute URL and tries to open it in a web browser.
I solved this issue by updating the binary that I was using.
I was using 0.8 and switched to 0.11.0 rc1.
Ensure that it is built against QT (the latest binary at http://code.google.com/p/wkhtmltopdf/downloads/detail?name=wkhtmltoimage-0.11.0_rc1-static-amd64.tar.bz2 is.
And then just to be sure enable internal links:
--enable-internal-links
when you call the conversion
i had this issue after installing pathced version of QT
i had wkhtmltopdf 0.9.6, than i also switched to 0.11.0 rc1
then worked fine!
and no need to use --enable-internal-links. you can just turn off this option by --disable-internal-links* by default its on.
Internal links appear only to work correctly in certain builds for certain platforms. With the latest WkHTMLtoPDF 0.12.5 releases the unix builds are OK (at least for Centos and Ubuntu) and internal links are generated correctly BUT windows builds DO NOT work and leave broken links. I don't know why this is and have commented on GitHub accordingly.
Also when multiple html input documents are used any 'internal' hyperlinks between these are broken (all platforms). In other words cross input document links are NOT fixed up. This would be a really useful feature addition (particularly when generating massive reports) but sadly does not appear to be supported as yet.
Do Magneto CE extensions work in PE? The extensions I've tried installing in PE aren't working (they install but yield blank screens) and I can't find a straight answer; don't know if it's a problem on my end or if it's built in to Magento. Thanks in advance!!
Short answer is yes. CE modules can function correctly as part of PE, but it will depend greatly on what parts of the functionality it touches.
Things to do for any Magento issues like this:
Ensure the extension is enabled (check to ensure it's output is enabled and it's active) - see this post for reference (the post is how to turn off an extension, but it will point you in the right direction)
Refresh your cache
Ensure logging is on and check your logs for errors
Check your web server logs - where these are will depend on which web server you are running. Apache logs are generally in the error.log file under /var/logs/apache2 or /var/log/httpd
If all else fails, start debugging, by putting Mage::log() entries into the code and seeing what is logged and what isn't
Any extension could possibly work in any version, even if it isn't listed as such. Generally developers of extensions just list the versions that it has been tested in, but that doesn't mean it cant be used in others.
Best way to find out is install the module in your dev environment, and test to make sure it isn't overwriting/breaking any of the existing functionality.
I just visited the Static Website Generation on Ruby toolbox and I don't know which of applications listed there is best suited for a little blog engine. Basically I need:
an index page with 1..5 of latest articles with shortened content;
possibility to add few main pages and a menu to access them (breadcrumb optional);
show articles
show/search archives
commenting system - Disqus Ok
tag-list cloud - optional
Look&Feel via layout
Important all content will be translated in 3 languages!
I can host on my own server, so side processing is possible.
Update:
First I'll try nanoc => blog's source on github
I think nanoc worth a try it has everything you specified, even if is not the best ranked on ruby toolbox its actively developed and highly customizable.
nanoc is a tool that runs on your local computer and compiles documents written in formats such as Markdown, Textile, Haml… into a static web site consisting of simple HTML files, ready for uploading to any web server.
and thats true :) I use it for a while not specially for a blog, but it has also helpers for that...
check out jekyll, it should work well for this.
Try my own "serious" - apart from archive search and tag cloud, it has everything you specified, plus the basic install should take you something like 5 minutes on heroku (and maybe 10 on your own server via Rack). It also has syntax highlighting, Disqus comments, Google Analytics and other goodies.
http://github.com/colszowka/serious
gem install serious
Disclaimer: It does not produce static html pages you can upload to your php vhost, though. But it uses caching and is really easy to setup and works on the free plan on heroku.