rvblog

1 – the ability to upload and store photo files across several folders rather than being restricted to having to upload everything into one single large folder.

2 – photo program to have the ability to retrieve photo files that are uploaded and stored in a folder that is located outside of the program’s main install folder (in other words – anywhere on the server).

3 – option to allow photo file names (beach_01.jpg) to be displayed in the gallery – saves having to manually enter a name for each photo file.

4 – ability to have thumbnails spread across several linked (and numbered) pages.

5 – don’t overload the program with stuff that few people will ever use – coppermine for example is too bloated with non essential features – stick with the basic requirements.

You should check out the gallery forum

https://gallery.menalto.com/index.php?name=PNphpBB2&file=viewforum&f=19&sid=aae7b76c09c98259c203c0c271895f00

@lmensel

1) What I do is look for a theme that looks close to the layout ( 1, 2, or 3 column) and the colour scheme that I like.

For theme ideas see: https://www.alexking.org/index.php?content=software/wordpress/themes.php

2) I upload the selected theme’s files to the wp-content/themes directory on the server and then make the theme active under the presentation section of my wordpress administration panel.

3) I then visit my site’s home page to view the active theme.

4) I look at the homepage’s source file and then I copy and paste the source code into an editor in order to create a “test.html” file.

5) I then copy the theme’s css file (usually “style.css”) to the “same directory” on my hard drive as the “test.html” file.

6) I make sure I change the path for the css file in the html file – it should be changed to something like this:

<link rel="stylesheet" href="style.css" type="text/css" media="screen" />

7) Then it’s simply a matter of playing around with the css file and making the changes that you want to make – after each change you can view the html file in a browser to see the results.

8) When you get the css file the way you want it – layout, positioning and style – replace the theme’s old css file with the new css file in the theme directory and go from there.

9) Any changes that you make to the “test.html” file itself (like adding extra div’s etc) must be made in the corresponding *.php file using an php editor.

10) Once I get my homepage to look close to what I want – I then repeat the process above to make other html files – example: “test2.html” to style comment boxes – “test3.html” to style the archive page, etc etc.

There are probably better ways to do it but this is how I started out and this system works great for me.

Have a look here:

https://ryanduff.net/archives/2005/04/04/feature-requests/

I’m currently using Ryan’s plugin on my site – It’s a great plugin – I was looking for something like this for a long time.

Because Ryan’s been busy with the popularity of his plugin and because he’s been great with helping me, I thought I would post the fix for the “email input box” issue that he sent me last night so that people can continue to use this great plugin.

The problem appears to be a conflict with any theme that uses the same label for “email” – try making the following changes to wp-contactform.php version 1.1 and it should correct the problem:

In lines 16 & 82:

change: id="email" to: id="contact_email"

In line 139:

change: for="email" to: for="contact_email"

In WP 1.5, Categories and Archives can be made to appear in a dropdown list – but “Pages” cannot.

I’ve asked for a “dropdown_pages” tag to be included in WP but that could take some time before the next WP update comes out – and who knows if the requested feature will be included.

I don’t know anything about php coding – so I cannot create my own plugins ( I wish I could ) but I’m trying to learn how template tags works to see if I can figure out a way to get my “Pages” to appear in a dropdown list.

Regarding the template tags issue – I’m still a bit confused here (and I hope that I don’t sound too lame here)

When coding a website using HTML, you simply add the HTML tag to an HTML page and your browser displays the results. The tag itself is not defined in your file – the tag is interpreted by the browser right?

On the other hand, I take it that all the template tags that are listed on the codex site need to be defined individually inside of the WordPress source code? Is that correct?

For example, if WordPress lacks a certain template tag feature and a new one is created, does the new tag have to be defined with WordPress in order to work?

Do the search utilities that you are talking about search for text in a file that is loaded into the utility itself, or, does the utility search your entire hard drive for a certain text string inside of any file (like a *.php file)

And can you recommend a good text search utility.

can you guys suggest a good search utility?

wp_list_pages is an example of one of the tags that I am looking for in the source code but I’m don’t know what *.php file it is defined in.

I could search through every wordpress source file – I just thought someone may already know off the top of their head the file that I’m looking for – saving me a whole lot of search time.

thanks

@neurofluoro

The original author of this plugin has posted an updated version 1.1

Get it here:

https://ryanduff.net/projects/wp-contactform/

See markdown bug fix here:

https://ryanduff.net/projects/wp-contactform/changelog/

thanks Kafkaesqui

@kafkaesqui

I get the same error with the theme-switcher.php plugin as I did with the preview_theme.php plugin

the following error appears at the top of my admin panel immediately after I activate the plugin:

Warning: Cannot modify header information – headers already sent by (output started at /usr/local/psa/home/vhosts/mysite.com/httpdocs
/wp-content/plugins/theme-switcher.php:2) in /usr/local/psa/home/vhosts/mysite.com/httpdocs
/wp-admin/admin.php on line 6

the error also occurs on line 7, 8 and 9

I looked at the mosquito site – but not sure where to add the request.

Guess I’ll have to wait for a plugin because I have no idea how to write one.

Thanks for the reply Kafkaesqui

@davincim:

The thread looks pretty straight forwards – thank you very much for your help