tignarius

Hi Michael

I have just done it again and this time it worked. I did nothing different the second time, so I ask, why did it not work the first time?

It is problems like this that make users reluctant to upgrade I suspect. Michael H. kindly installed 2.1.2 for me twenty days ago which was a couple of days before 2.1.3 was released. I have not dared to even try to do the upgrade until now that I have been messing around with WordPress for a couple of weeks.

I am still trying to install plug-ins to make the site do what I would like it to do. I am having an enormous issue with a coppermine integration plug-in but cannot seem to get any help from here or its author. For me, it is worries like this that make upgrading a challenge to say the least.

Brilliant…….!

So I, (who know nothing) follow the detailed instructions on how to upgrade and this is what I get;

Warning: main(C:\Inetpub\vhosts\scotsheraldry.com\httpdocs\blog/wp-includes/wp-db.php): failed to open stream: No such file or directory in C:\Inetpub\vhosts\scotsheraldry.com\httpdocs\blog\wp-settings.php on line 100

Fatal error: main(): Failed opening required ‘C:\Inetpub\vhosts\scotsheraldry.com\httpdocs\blog/wp-includes/wp-db.php’ (include_path=’.;./includes;./pear’) in C:\Inetpub\vhosts\scotsheraldry.com\httpdocs\blog\wp-settings.php on line 100

Suggestions please

It would seem to me that this some kind of ‘path’ error (maybe)! Can anyone advise how to change this path to make the thing work?

Thank you

When I try to configure this Plug-in I get the following error message;

Warning: main(C:\\Inetpub\\vhosts\\scotsheraldry.com\\httpdocs\\blog\\wp-content\\plugins\\coppermine/wp-blog-header.php): failed to open stream: No such file or directory in C:\Inetpub\vhosts\scotsheraldry.com\httpdocs\blog\wp-content\plugins\coppermine\coppermine-config.php on line 1375

Fatal error: main(): Failed opening required ‘C:\\Inetpub\\vhosts\\scotsheraldry.com\\httpdocs\\blog\\wp-content\\plugins\\coppermine/wp-blog-header.php’ (include_path=’.;./includes;./pear’) in C:\Inetpub\vhosts\scotsheraldry.com\httpdocs\blog\wp-content\plugins\coppermine\coppermine-config.php on line 1375

This seems to me to be some kins of ‘path’ errror. Has the structure of WordPress changed so much in the last 8 months to make it impossible for me to use this plug-in?

Is there anyone out there who can help please?

I think I have the files in place but I can’t run the configuration. I get the following error message
Further;

Warning: main(C:\\Inetpub\\vhosts\\scotsheraldry.com\\httpdocs\\blog\\wp-content\\plugins\\coppermine/wp-blog-header.php): failed to open stream: No such file or directory in C:\Inetpub\vhosts\scotsheraldry.com\httpdocs\blog\wp-content\plugins\coppermine\coppermine-config.php on line 1375

Fatal error: main(): Failed opening required ‘C:\\Inetpub\\vhosts\\scotsheraldry.com\\httpdocs\\blog\\wp-content\\plugins\\coppermine/wp-blog-header.php’ (include_path=’.;./includes;./pear’) in C:\Inetpub\vhosts\scotsheraldry.com\httpdocs\blog\wp-content\plugins\coppermine\coppermine-config.php on line 1375

Would be grateful if you can help

Further; Although I think I might have the upload correct now I cannot get the plug-in to configure. I get the message;-

Warning: main(C:\\Inetpub\\vhosts\\scotsheraldry.com\\httpdocs\\blog\\wp-content\\plugins\\coppermine/wp-blog-header.php): failed to open stream: No such file or directory in C:\Inetpub\vhosts\scotsheraldry.com\httpdocs\blog\wp-content\plugins\coppermine\coppermine-config.php on line 1375

Fatal error: main(): Failed opening required ‘C:\\Inetpub\\vhosts\\scotsheraldry.com\\httpdocs\\blog\\wp-content\\plugins\\coppermine/wp-blog-header.php’ (include_path=’.;./includes;./pear’) in C:\Inetpub\vhosts\scotsheraldry.com\httpdocs\blog\wp-content\plugins\coppermine\coppermine-config.php on line 1375

Does anyone know what this means or how I can fix it?

I really would appreciate some help here even if it is just to track down Stilgar (Martijn van der Kwast)himself!

https://www.stilglog.com/wordpress-plugins/coppermine-plugin/

but you should bear in mind I cannot get it to configure and I cannot raise Stilgar (Martijn van der Kwast) to get a solution to the install problem….

Ok. My brain now hurts… but I have now managed to install the copperminesc plug-in without any help.

It is supposed to be capable of all sorts of marvelous things but now has me totally stumped as to how to use it. I suppose I was expecting some kind of user dashboard or dashboard extension but there does not seem to be anything…..!

Any ideas anyone?

Tone down the white lettering. It does hurt the eyes. On my CRT monitor it is blindingly bright. It might not be so bright on flat-screen monitors I suppose….

Thank you Whooami. Does anyone else have a view or indeed, better still, a solution to my problem?

Yes, I see your point Handysolo, but essentially the image is aready up on the web in the Whooami case. In my instance I am looking to post the image into the blog from ones machine rather than ‘link’ it.

The ‘villageidiot’ site appears to be whooami’s own site so he does presumably know how his site works. The operative as far as his option working seems to be that the picture is “hosted already” which I asume to mean that the image is alread in his database but used in another thread. What I am trying to do is give users above a certain degree the caperbility of posting/uploading a new image into a comment.

I suppose essentially I would like to give the user (above that certain degree)the loggin ‘write a post’ posting screen. Alternatively is is possilbe to use the loggedin’ Write a new posting’ page to write a comment….?

With the greatest respect to LaaTINO’s thoughts, does anyone have a definative answer to this question. I ask because, I want my registered users (above the level of author)to be able to debate design ideas with illustrations in their posts.

My WordPress blog has only been loaded for one week and I am still trying to make it useable for my site users. I haven’t even cracked the side-bar yet let alone added some of the features I need for it to match the capabilities of the old HTML site. So an un-necessarily complicated upgrade is totally unwelcome.

I am glad to see that I managed to identify WordPress’s second biggest problem within a week of becoming a user…