andynz

I have the same question.

Andy

I do not know if this relates to my problem. My hosting company in NZ has disabled my IP address due to what they believe is a vulnerability in WP Photo Album Plus version 8.0.06.004
They specifically refer to the following files:
/js/wppa-spheric.js
/js/wppa-zoom.js
/js/wppw-ajax-front.js
/js/wppa-slideshow.js
/js/wppa-utils.js
Is it possible to replace with an earlier version which does not have this problem.

Andy

Thanks, that worked perfectly on another website where WP photo album 8.0.06.004 is installed.
Set max cover width to 400
Cover type to Standard mcr
Now in 3 columns

Cannot find the cover type option for version 7.7.05.003 so will fix it when I update the version.

Andy

Thanks for taking the trouble to reply, but your suggestion doe not really address the problem which is:
How do I include an email address in the mail template (to, cc, bcc, 2nd email or wherever) if the email tag may be empty?

Andy

Yes, it did for me too.
Sorry for the confusion, but I have been trying out various options on my test site.
I will shortly put back the password on my test site, so thanks for your help.

By the way, I picked up another of your hints while browsing the forum. I wanted to avoid the blank lines between list items and found that this does the trick:
.tablepress ul br,
.tablepress ul+br {
display: none;
}

Will now give you a well-deserved 5-star rating.
Andy

Thanks, Tobias, that is very helpful.
I have been experimenting and find that left and right margins of -24px is a big improvement (not so bothered about top and bottom).
Padding-left of 22px makes sure that the content is lined up with other cells, but have left padding-right unchanged for now (still experimenting).
Regards
Andy

Thanks Tobias, thead worked fine. Removing the heading meant that the width of the table defaulted to the minimum so I added CSS to set the table width to 100%.

If you come up with a solution to (2), I would be interested – but that would just be an added bonus. Perhaps, it is better to leave it as it is for consistency with responsive=collapse, which I also use extensively.
Andy

Thanks very much for your prompt advice.
All looks OK now, by adding a border to the .row class and padding to the .field class.
Andy

Sorry that I forgot to unset protection – should be OK now.
Will experiment with CSS styling as you suggest.
Andy

Thanks very much for the quick response.
I made the change that you recommended and that seems to have done the trick.

Andy

Your advice has been really helpful, so I have one more question before I carry out the migration (on a real website – not my test one).
WordPress has been installed in /root/wordpress and the settings are:
WordPress Address: https://dancescottish.org.nz/wordpress
Site Address: https://dancescottish.org.nz/wordpress
Permalinks: Postname

/root/wordpress includes the required .htaccess and index.php files
Website addressed as dancescottish.org.nz/wordpress works fine as it is.

If I display a page in the admin panel, say with title ‘Class Guidelines’ the permalink is displayed as expected
Permalink: https://dancescottish.org.nz/wordpress/class-guidelines/ ?

The question is: When I change the site address in WP settings to:
Site Address: https://dancescottish.org.nz
will WP automatically change all the permalinks to exclude /wordpress
and take care of any links which have been defined in the menu.

If so, I just need to correct any hard-coded links in my pages, tablepress etc and. of course, set up modified versions of .htaccess and index.php in /root.

And, before you ask, /wordpress and the database will be backed up first!

Regards
Andy

Thanks for the answer.
You raised a very important point about internal links to pages since my tests had shown that these no longer work unless I remove the /wordpress part of the path. I had hoped that there might be some nifty way of leaving the path as it is, but I now know that this is not the case.
Fortunately there are very few of them.

Regards
Andy

Just one other related question.
I am replacing a non-WordPress website (dancescottish.org.nz) in /root
with a WordPress site (same domain name) which is being developed in /root/wordpress.
Thus it is currently addressed as dancescottish.org.nz/wordpress which is the site address in the WordPress settings.

My plan is to launch the new website in /root by:
– setting up index.php in /root
– setting up .htaccess in /root
– changing the site address in WordPress to dancescottish.org.nz

However, I want to test this out before the final launch. This means doing all the above, including changing the site address in WordPress. Then, having assured that it works, reinstate the old website for a couple of weeks. Then repeat the changes which are then permanent.

This may not seem to be a sensible approach, but there are logistical reasons why it may be necesssary.

So, my question is: Are there technical reasons why changing the site address in WP back and forth is inadvisable? I have tried this on a test site and it seems OK.

In fact, I concluded that I could carry out my test by just changing the two /root file and leaving the WP site address as dancescottish.org.nz/wordpress. I could still activate the website by either:
dancescottish.org.nz
or
dancescottish.org.nz/website

Andy

Thanks for the confirmation and explanation. All makes sense now.
Andy

Rajan, thanks for taking the trouble to reply.

However, https://rotorua.waibopscd.org.nz/wordpress/links/ works exactly as it should by redirecting to the root. No 404 error as occurs with the home page.

Jadenjoner may have a clue to the answer. I probably set the website up originally with default permalinks and changed it to postname later. This might have confused wordpress.

As for why I install WordPress in its own directory, I think this a fairly common strategy.