JFolder::create: Could not create directory Path: /var/www/html/t3-assets - joomla3.5

Joomla! 3.6.5
After install T3 template,a warning popup while I click T3 in template manager.
JFolder::create: Could not create directory Path: /var/www/html/t3-assets
I have tried to modify the $log_path and $tmp_path,but it doesn't work.

After trying many methods,I finally found the problem..
It's access problem,
chmod 777 html
and reinstall the T3 template.
It's OK!

Related

How to override CSS file in custom theme in magento 2

In Magento 2, I have create new theme. I tried to add less file app/design/frontend/mage_vender/sample(theme)/web/css/source‌​/_extend.less.
But it is not showing changes.
Please can anyone tell me, how can we do ?
I am using magento 2.1.3
Thank you
The first thing you need to do is to create your theme, don't forget to add all the required files like the theme.xml and registration.php. Last time I checked the magento 2 documentation it was up to date and had enough information regarding on how to create new themes.
Second thing you need to do is to add your new theme to the theme.js, other wise you will not be able to compile your new less files into CSS. You do this by adding a new json group into /dev/tools/grunt/configs/themes.js
Now to override less files for example lets says the _navigation.less you just need to put it under /app/design/frontend/[YOUR_THEME]/web/css/source/_navigation.less
Then do a grunt refresh, you do this always when you add new files and grunt watch if you're editing one that has already been added.
We have another way to do it.
First, create a new less file and then add it inside your _extend.less file like below.
#import 'theme/slick.less';
After that, if you use grunt then need to do the below things.
/dev/tools/grunt/configs/themes.js
<theme_name>: {
area: 'frontend',
name: '/',
locale: en_US,
files: [
'<path_to_file1>', //path to root source file ex: css/styles-m
'<path_to_file2>' ex: 'css/styles-l'
],
dsl: 'less'
After adding the above please run the below commands.
grunt clean:theme
grunt exec:theme
grunt less:theme
chmod 0777 -R var/*
chmod 0777 -R pub/*
chmod 0777 -R generated/*
grunt watch
Please check and let us know if you still facing any issues.

opkg install error - wfopen no such file or directory

I have followed instructions to create an .ipk file, the Packages.gz and host them on a web server as a repo. I have set the opkg.conf in my other VM to point to this repo. The other VM is able to update and list the contents of repositories successfully.
But, when I try to install, I get this message. Can you please describe why I am getting this and what needs to be changed?
Collected errors:
* wfopen: /etc/repo/d1/something.py: No such file or directory
* wfopen: /etc/repo/d1/something-else.py: No such file or directory
While creating the .ipk, I had created a folder named data that had a file structure as /etc/repo/d1/ with the file something.py stored at d1 location. I zipped that folder to data.tar.gz. And, then together with control.tar.gz and 'debian-binary`, I created the .ipk.
I followed instructions from here:
http://bitsum.com/creating_ipk_packages.htm
http://www.jumpnowtek.com/yocto/Managing-a-private-opkg-repository.html
http://www.jumpnowtek.com/yocto/Using-your-build-workstation-as-a-remote-package-repository.html
It is very likely that the directory called /etc/repo/d1/ does not exist on the target system. If you create the folder manually, and try installing again, it probably will not fail. I'm not sure how to force opkg to create the empty directory by itself :/
Update:
You can solve this problem using a preinst script. Just create the missing directories on it, like this:
#!/bin/sh
mkdir -p /etc/repo/d1/
# always return 0 if success
exit 0

Magento Extension Installation Error

I am new to Magento. And when i m trying to Install New Extensions using this key: - http://connect20.magentocommerce.com/community/Netz98_ModuleCreator. everything works perfect but after clicking on install button and then to proceed button i am getting the following error..
Checking dependencies of packages
Installing package community/Netz98_ModuleCreator 1.0.0
CONNECT ERROR: Failed to open file /var/www/downloader/.cache/community/Netz98_ModuleCreator-1.0.0/moduleCreator/Templates/Blank/app/code/local/Namespace/Module/Block/Adminhtml/Module/Edit/Tab/Form.php
I tried to solve but couldn't help it.. can anybody have solution for it??? any answer is appreciable..
https://stackoverflow.com/a/26436345/4155825
same bug i guess. I try this and solved my problem.
[quote]
In file downloader\lib\Mage\Archive\Tar.php find method _extractFileHeader().
Then find the code:
if (!($header['name'] == '././#LongLink' && $header['type'] == 'L')) {
$header['name'] = trim($header['name']);
return $header;
}
And replace it with:
if (!(trim($header['name']) == '././#LongLink' && $header['type'] == 'L')) {
$header['name'] = trim($header['name']);
return $header;
}
Hope this will help you.
From my experience, chmod -R 777 downloader doesn't work. -R doesn't seem to go all the way down when there are a lot of directories.
I had to go further down and chmod -R 777 /var/www/downloader/.cache/community/Netz98_ModuleCreator-1.0.0/moduleCreator/Templates/Blank/app/code/local/Namespace/Module for it to set the proper permissions on the deeper directories.

fuseki load graph - s-put not found

I am trying to load a graph in fuseki. The server is working as it should.
But when I try s-put inside the fuseki folder it tells me s-put is not found?!
hdeus$ ls
DEPENDENCIES config.ttl s-delete
Data fuseki s-get
LICENSE fuseki-server s-head
NOTICE fuseki-server.bat s-post
ReleaseNotes.txt fuseki-server.jar s-put
config-examples.ttl fuseki_config.ttl s-query
config-inf-tdb.ttl log4j.properties s-update
config-tdb.ttl pages s-update-form
hdeus$ sudo ./s-put http://localhost:3030/ds/data default Data/books.ttl
sudo: ./s-put: command not found
Any idea what the problem might be? I tried copy/paste s-put from the ls output but stil nothing... I am working in mac os X
Is the file executable? If you unpacked from the zip file, you need to set the s-* executable. Also, you need ruby installed.

Magento: upgrade pre 1.6 version to most recent one

I've seen a lot of questions about pre 1.6 Magento installations to the most recent version (at the current moment 1.7.0.2) but there are a lot of answers that don't work for everybody.
So below the answer to the question:
How to upgrade Magento from a pre 1.6 installation to the most recent one.
There are a lot of versions and not all of them are working. This one has worked for me for a lot of versions, as far as 1.3 to 1.7.
Please add comments with solutions to problems you're experiencing, I can update the answer so other people get help from this topic too!
What you need:
- SUDO rights/root account on your server.
- The linux package 'nohub'
- make sure NOBODY can trigger the index.php. If your version supports maintenance.flag, put an empty maintenance.flag file in your Magento root.
Walkthrough
1) Download the latest Magento. Overwrite: ./download/* ./lib/* ./mage
2) Run these steps from you Magento root als SUDOer (if you're not root, put 'sudo' for all the commands)
find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;
chmod -R 777 ./var
chmod 550 mage
3) Go to your Magento root folder and type:
./mage list-upgrades
./mage config-set preferred_state stable
./mage upgrade-all --force
./mage install http://connect20.magentocommerce.com/community Mage_All_Latest --force
4) Now there is the last step. Note: In some situations this process can take up to 8+ hours!
nohup php -f ./index.php
Known issues
1) it's possible that your update gets in a loop. To find this loop, enable debugging.Edit: /lib/Varien/Db/Adapter/Pdo/Mysql.php (+/- line 112 and 112)
protected $_debug = true;
protected $_debuglogeverything = true;
This will write a debug to: /var/debug/[debug_file]
2) Read the file by opening the dir:
cd /var/debug/[debug_file] <-- replace with the actual filename
tail -f [debug_file]
3) If you use debug, the file will get HUGE! Make sure you delete it once in a while.
Tip: as a root user, type:
crontab -e
*/5 * * * * rm /[my_magento_base_folder]/var/debug/[debug_file] <-- add this line
If you want to read the file, add a # to this line and use tail to read it.
These steps help you find common errors and loops (if the tail shows a repeating error message)