Fatal Error After Upgrading to 4.1.4

sjoudi · July 3rd, 2011, 04:49 AM

Hi:

After upgrading to vBulletin Suite 4.1.4, I am facing the below fatal error:

Warning: require_once([path]/includes/functions_wysiwyg.php) [function.require-once]: failed to open stream: No such file or directory in [path]/includes/functions_gallery.php on line 729

My current vbGallery is 3.0.1

Please advice
Samer

Chuck S · July 3rd, 2011, 08:06 AM

There is no support currently for the ckeditor in vb 4.14 your only way to solve that issue is to upload that file from 4.13 but your comment editor is only going to be a blank box.

Subah · July 3rd, 2011, 11:16 AM

Or disable the vBGallery

Chuck S · July 3rd, 2011, 01:10 PM

yes but doing above will allow the gallery to work while support for ckeditor is being looked at.

sjoudi · July 4th, 2011, 01:10 AM

Thanks, it is working fine now... I have uploaded the file from the previous version.

When will the next version of vbGallery hit the street?

Chuck S · July 4th, 2011, 08:11 AM

There is no determined date as vbGallery has not hit a development cycle yet. Right now Pro 8 is in development. Looking at supporting the new ckeditor is something we have to do globally to all our applications.

myuption · July 28th, 2011, 12:00 PM

It's been a month and no updates for vbG?

Pro 8 shouldn't stop development of vbG, those are different products.

Now vB released 4.1.5. Something is not right on your dev cycles. And that has happened since the very start. Too bad I have to stop forum upgrade because of the gallery.

Chuck S · July 28th, 2011, 12:15 PM

It took almost a year for us to write a vb4 compatible version of vbgallery after vb4 was released. We had access to vb4 only 3 months before it was gold. What is not acceptable is how Internet Brands has changed there policies and access times to beta software.

Giving a couple weeks or changing an editor completely in a minor revision dot release ie ( between 4.13 and 4.14 ) which are suppose to be bug releases with developers having no access to the code to be compatible you can not expect an immediate fix.

We are compatible with vbgallery up to 4.13.

We are an extremely small company with couple people only so when we have time to look into vbGallery we will but we do have 4 products that we release.

Chuck S · July 28th, 2011, 02:37 PM

By the way you can redownload the source code and reupload all the files and you should not have any errors. That will be the only patch there is until we have full time to investigate and decide how to proceed with vbGallery.

myuption · August 5th, 2011, 10:39 AM

That's not the issue Chuck, and if I recall, after developers complain in vB now there are Beta versions of the upcoming forums and suite available.

Those 4.1.5 Beta have been there for a month or so. It seems Luc is the only one developing vBG, haven't read much of him in weeks

Chuck S · August 5th, 2011, 01:20 PM

No What I am saying and have said along time now. One month is not enough time to give developers to support changes especially when those changes are being made in a .0x release which is very short development time to begin with. Completely redoing an editor in that type of release most companies would not do. Those types of releases are for bug fixes. You do not release major revisions and they did. Developers use to have a six months to a year or so before when vbulletin wrote new code that drastically changed things.

We are in the middle of a development phase on Pro we do not have the resources to drop what we are doing and do work on something else. We are a very small company.

With that said

I have already patched most of the products to work with the new code minimally.

vbGallery 3.01 will work fine with the new 4.14 or 4.15 now if you simply redownload the build and upload all the files except the vbgallery config file. I altered the build to work with the new code. We do not support the full editor yet but you can comment without issues which from a support perspective we did until we can decide which way to go.

It will take time to see what levels in integration we will support.

sross · December 19th, 2011, 04:39 PM

My commenting works at a basic level, but if a user edits then all formatting is lost. Also, my error logs are flooded with vbgallery errors related to ckeditor issues 1,000's of them and I'm having to frequently clear out gig+ error log because of this. Forcing vbulletin to not use ckeditor is unrealistic especially on a large board. The ideal solution is to ensure that the gallery uses a vanilla editor. It appears this is happening, but it's very dirty as it's flooding up my server with errors related to ckeditor issues. If possible can vbgallery coders simply code it to use the standard vbull editor on gallery pages rather than a broken ckeditor? It also appears these errors are increasing my server load. Thanks

Chuck S · December 19th, 2011, 05:11 PM

vbgallery does not use the ckeditor at least it doesnt in our downloaded code now. It should be a simple basic commenting box. There are no displayable errors in the vbgallery downloaded code in the members area. The commenting level offered is a basic comment box only.

ausphotography · April 14th, 2012, 06:08 PM

We are running vB4.1.12 with the basic comment box -- no issue with that.

4.1.12 is the last 4.1.x and 4.2.0 will be feature heavy.

Maybe its time to at least have a maintenance release of vB Gallery and remove the dependency on the includes/functions_wysiwyg.php file.

I posted a warning about deleting this file here as there is a discussion about cleaning up deprecated files on vb.com.
https://www.vbulletin.com/forum/show...=1#post2283599

As for ckeditor support -- we can wait for that as long as vb gallery continues to work.

Thanks!

Chuck S · April 14th, 2012, 06:23 PM

From what I can tell we do not call for functions_wysiwyg.php in vbgallery 3.01 for vb4

We took care of that issue along while ago.

ausphotography · April 15th, 2012, 04:07 AM

But the file is still in a require_once statement functions_wysiwyg.php.

Chuck S · April 15th, 2012, 08:34 AM

I looked at our downloaded code from our members area before I posted here. There is no require statement for functions_wysiwyg.php

Look at the date of this thread. We have resolved any issues that have been reported so there should be no errors.

ausphotography · April 16th, 2012, 06:53 PM

We are running vB gallery 3.01 and if functions_wysiwyg.php is missing I get errors??

Are you saying to re-download?

FWI... doing a find/grep...

/home/apforum/public_html/gallery/browseimages.php: require_once(DIR . '/includes/functions_wysiwyg.php');
/home/apforum/public_html/gallery/newreply.php: require_once(DIR . '/includes/functions_wysiwyg.php');
/home/apforum/public_html/gallery/index.php: require_once(DIR . '/includes/functions_wysiwyg.php');
/home/apforum/public_html/gallery/showimage.php: require_once(DIR . '/includes/functions_wysiwyg.php');
/home/apforum/public_html/gallery/ecard.php: require_once(DIR . '/includes/functions_wysiwyg.php');

Chuck S · April 16th, 2012, 07:10 PM

Yes I would like I said your referring to issues from a year ago.

ausphotography · April 16th, 2012, 07:59 PM

Ok, thanks!

Maybe bump the version number