Sometimes you have to change the base domains of your blog. Therefore there are the following possibilities (ATTENTION: These snippets are thought to be used with a single site installation): Backend settings If you have access to the Backend of your WordPress installation, you can change the basedomain of your blog under: Settings -> General -> WordPress […]
WP-CLI (http://wp-cli.org/) is a great commandline tool to manage your WordPress installation. It has countless commands. For example to: change database settings clear the cache manage comments and posts install plugins … The “normal” installation is well documented on the project page. But I prefer to store my project tools (f.e.: vagrant, coposer, etc.) in […]
This snippet shows how to call a REST-API via curl. It also tells you how you can do a Basic-HTTP-Authentification to legitimate the call.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 |
This snippet shows how to call a REST-API via curl. It also tells you how you can do a Basic-HTTP-Authentification to legitimate the call. // Get it the REST way over Curl $mCurl = curl_init(); curl_setopt($mCurl, CURLOPT_URL, $sEndpoint); curl_setopt($mCurl, CURLOPT_RETURNTRANSFER, true); curl_setopt($mCurl, CURLOPT_HTTPAUTH, CURLAUTH_BASIC); curl_setopt($mCurl, CURLOPT_USERPWD, "$sUsername:$sPassword"); // Authentication via http-auth curl_setopt($mCurl, CURLOPT_RETURNTRANSFER, 1); $mCurlResponse = curl_exec($mCurl); if(!$mCurlResponse){ throw new Exception("Rest call failed! Call-Data:\n" . print_r(curl_getinfo($mCurl), true)); } // deal with return http-codes: // 200 (all Codes starting with 2xx): Call and processing where successful. // 400 (all Codes starting with 4xx): Call fails - request contains failure // 500 (all Codes starting with 5xx): Server processing failure $sStatusCode = curl_getinfo($mCurl, CURLINFO_HTTP_CODE); $sCallUrl = curl_getinfo($mCurl, CURLINFO_EFFECTIVE_URL); echo $mCurlResponse . "\n"; curl_close($mCurl); // OK if($sStatusCode >= 200 && $sStatusCode < 400){ //make a SimpleXML Object out of response libxml_clear_errors(); //clear Error Buffer libxml_use_internal_errors(true); //put on error collection #$oXml = simplexml_load_file('/var/www/typomage/app/code/local/SHELDON/Tradebyte/ExcampleData/products.xml'); $oXml = simplexml_load_string($mCurlResponse); if(!$oXml){ $aErrors = libxml_get_errors(); // get xml parsing errors throw new Exception("Error on loading response XML!:\n" . print_r($aErrors)); } return $oXml; } // Call fails - request contains failure elseif($sStatusCode >=400 && $sStatusCode < 500){ throw new Exception("Call fails - request contains failure! ($sStatusCode)\nCall was: $sCallUrl\n\nRaw-Return:\n$mCurlResponse"); } // Server processing failure elseif($sStatusCode >= 500){ throw new Exception("Server processing failure! ($sStatusCode)\nCall was: $sCallUrl\n\nRaw-Return:\n$mCurlResponse"); } // Unexpected status else{ throw new Exception("Unexpected HTTP-Status-Code! ($sStatusCode)\nCall was: $sCallUrl\n\nRaw-Return:\n$mCurlResponse"); } |
To do this you only have to add a api2.xml in your modules etc folder that puts the necessary product tags into the node /config/api2/resources/product/attributes (xPath):
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 |
<config> <api2> <resources> <product> <attributes> <sheldon_ean>EAN</sheldon_ean> <sheldon_articlenbr>Articlenumber (Model)</sheldon_articlenbr> <sheldon_stylenbr>Stylenumber</sheldon_stylenbr> <sheldon_color>Color</sheldon_color> <sheldon_size>Size</sheldon_size> <sheldon_material_description>Material Description</sheldon_material_description> <sheldon_supplement>Supplement</sheldon_supplement> <sheldon_carehints>Carehints</sheldon_carehints> <sheldon_is_aboable>Is aboable product</sheldon_is_aboable> <sheldon_is_sale_product>Is sale product</sheldon_is_sale_product> <sheldon_is_new_product>Is new product</sheldon_is_new_product> <sheldon_is_reddot_product>Is reddot Product</sheldon_is_reddot_product> <sheldon_reddot_years>Product Reddotyears</sheldon_reddot_years> <sheldon_is_airberlin_reduceable>Airberlin discoutable</sheldon_is_airberlin_reduceable> <sheldon_color_filter>Color Filter</sheldon_color_filter> <sheldon_denier_filter>Denier</sheldon_denier_filter> <sheldon_shape_filter>Shape</sheldon_shape_filter> <sheldon_function_filter>Function</sheldon_function_filter> <sheldon_gloss_filter>Gloss</sheldon_gloss_filter> <sheldon_material_filter>Material</sheldon_material_filter> <sheldon_pattern_motif_filter>Pattern / Motif</sheldon_pattern_motif_filter> <sheldon_structure_filter>Structure</sheldon_structure_filter> <sheldon_structure_pattern_filter>Structure / Pattern</sheldon_structure_pattern_filter> <sheldon_transparency_gloss_filter>Transparency / Gloss</sheldon_transparency_gloss_filter> <sheldon_season_filter>Season</sheldon_season_filter> <description>Description</description> <short_description>Short-Description</short_description> </attributes> </product> </resources> </api2> </config> |
After that you can edit your REST-Attribute permissions, where you’ll find the newly defined attributes. Then a call to die products -API will show you the new Attributes.
To use the Magento REST_AP it is necessary to set the following configurations in .htaccess: change Options +FollowSymLinks to Options +FollowSymLinks -MultiViews insert RewriteRule ^api api.php?type=rest [QSA,L] directly under #RewriteBase /magento/
To use busware SCC boards (see busware shop) with FHEM you have to: Install FHEM (see my earlier blogpost) If not already root
|
1 |
$> sudo su - |
Remove all reverences of the device ttyAMA0 (/dev/ttyAMA0) from /etc/inittab and /boot/cmdline.txt (if you use a Banana Pi you should look for ttyS2)
|
1 |
$> nano /etc/inittab |
and replace
|
1 2 |
#Spawn a getty on Raspberry Pi serial line T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100 |
with
|
1 2 |
#Spawn a getty on Raspberry Pi serial line #T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100 |
and
|
1 |
$> nano /boot/cmdline.txt |
and remove “console=ttyAMA0,115200” so […]
To install FHEM into /opt/fhem you have to take the following steps: Switch to root mode: $> sudo su - Get archive key and add it to system keys: $> wget -qO - http://debian.fhem.de/archive.key | apt-key add - Add reposetory to your system sources: $> nano /etc/apt/sources.list and add the following line to the bottom : deb http://debian.fhem.de/stable ./ Update sources: $> apt-get update Update system: $> apt-get upgrade Install FHEM: $> apt-get install fhem This will install all […]
To install Rasbian on a SD-Card you have to follow these Steps Format SD-Card Fat32 (f.e. with GParted http://gparted.org/) Download Raspbian (or any other operation system) from http://www.raspberrypi.org/downloads/ Extract the downloaded zip-file Find out what is the devicepath of your SD-Card (you can use the df-command or get a list of partitions via linux-list-of-partitions) Execute the […]
|
1 |
int value = map(input, minOldRange, maxOldRange, minNewrange, maxNewRange); |
If you have problems to get rid of FHEM, because of some package inconsistencies cause by broken installation or so, you can do this:
|
1 2 |
$> sudo dpkg --remove --force-remove-reinstreq fhem $> sudo apt-get-update -f |
This blog uses cookies to give you the best user experience. If you continue to use this site, we assume that you agree with it.
OK
Decline
More Information
