copy norikoguide.pepper.jp/en ->  norikoguide.pepper.jp/tgnwork

1. Use old FFFTP on old NEC xp.;  copy all files from /en/   to  /tgnwork  @17/10/27

2. Duplicate database with different prefix.; Time limitation at Lolipop is inconvenient, so that database is better exported to home debian;  manipulating at debian-home: tables with wp1_ prefix are duplicted to tables with wp1c_ prefix; then import into original database@lolipop.

2.1. export database LAA0242974-f1qyds @norikoguide.pepper.jp :Note: in zip (important!)

2.2. import into database wpkiyoshi (wpnakym)( this serves as working database) @192.168.0.17

2.3. on wpkiyoshi(wpnakym): delete tables other than wp1_ , then change prefix wp1_ to wp1c_, then export it.

2.4.  import exported working database into original database LAA0242974-f1qyds @norikoguide.pepper.jp

3.

Screen option on widget page( appearance->widget) will toggle display.

1. Web Server Ownership
The first level is actually to make sure that your web server has ownership over the directories:
chown -R www-data:www-data your-wordpress-directory

2. Directory Permissions
The second level is also required – you must make sure that the directory permissions are properly set:
sudo find /var/www/wordpress/ -type d -exec chmod 755 {} \;
sudo find /var/www/wordpress/ -type f -exec chmod 644 {} \;

I’ve found that most solutions posted on the web show part two but skip the first part.

<?php
$args = array(
‘post_type’ => ‘kyoto_courses’,
‘taxonomy’ => ‘courses_kyoto’,
‘term’ => ‘kobe-standard-tours’,
‘orderby’=>’title’,
‘order’=> ‘ASC’    ); ?>
<!–<?php query_posts( $args ); ?>–>
<?php get_posts( $args ); ?>
————————————————-

Note that default is:  ‘order’=> ‘DSC

( Also default: ‘orderby’=>’date”)

<script type=”text/javascript” src=”<?php echo get_stylesheet_directory_uri(); ?>/js/heightLine.js” defer ></script>

.popList li a {display:block;}

.popList li a:hover{ background-color:Aqua;}/*#00ffff*/

margin collapse is very tricky and might be buggy.

You better overwrite the ancesters’ margin.

Never!!

With this blank line, permalink to default will cause “not found”.

Correct .htaccess when the permalink is %postname% will be rewritten to almost blank .htaccess when the permalink is set  to default, and will be written back to the original file when the permalink is reset to %postname%.