Foreign characters

Lionel · July 27th, 2005, 12:33 PM

How can I avoid these sort of things in title or description?

J\'ai besoin de toi Alan Cave

the "\" before the apostrohe.

Chuck S · July 27th, 2005, 12:34 PM

What software you running and what version

Lionel · July 27th, 2005, 12:36 PM

I am running 2.91 review post downloaded a week ago.
I commented out the fixed message in front of description to allow html

sorry looks like I posted the wrong place.

Lionel · July 27th, 2005, 12:54 PM

ok, I made it
$desc = stripslashes($desc);

and that seems to work.

Chuck S · July 27th, 2005, 01:22 PM

Okay thats good that worked and reviewpost 3.0 should be out shortly that is a complete rewrite and fixes any issues

Lionel · July 27th, 2005, 01:28 PM

Oh Lord. I customized 2.91 heavily... The main thing that I did was to split showproduct into 3.

Question: Which variables get parsed in showcat? I am integrating with vbulletin, forcing a template set which is not user selectable. I am able to do this all over my site defining the pages as vbadvanced. When I do it with reviewpost, it works, except that showcat is empty. Usually that happens when you need to tell vbadvanced which variable to parse in the page.

If I don't do that with vbadvanced, reviewpost will not accept the forced style.

Chuck S · July 27th, 2005, 02:08 PM

Well I cant really comment on a hack you have but in Reviewpost 3.0 there is this code which allows for you to create additional template sets.

if ( is_dir( "$RP_PATH/{$Globals['TMPL_PATH']}/$styleid" ) ) {
$Globals['TMPL_PATH'] = "{$Globals['TMPL_PATH']}/$styleid";
}

Thus say if you run template blah blah with a styleid of 6 you can create a directory under templates/vbenhanced named 6 and then copy a new set of vbenhanced templates into that directory and then modify them as needed. Photopost and Classifieds already have this feature although most people do not use it. If the directory say 6 does not exist and your using vb3 then the template directory defaults back to templates/vbenhanced

Lionel · July 27th, 2005, 02:16 PM

I am already forcing any vb style with 2.91, as long as the style is user selectable. It just won't force non user selectable.

For example, on my pages, regardless of global user choice of vbstyle, it will display always in same forced style. I just have to do those vb2 buttons over.

Chuck S · July 27th, 2005, 02:30 PM

Well what I am saying is this.

If you set $styleid in Vbulletin to 6 for the default theme then in Reviewpost 3.0 as long as you have a reviewpost template set under /templates/vbenhanced/6 it should load that template set

Lionel · July 27th, 2005, 02:34 PM

never mind

Chuck S · July 27th, 2005, 02:38 PM

Okay well you can do whatever you wish to do and hack files however. I am merely pointing out how our product is coded.

Lionel · July 27th, 2005, 02:42 PM

Sorry, will not try to help again

Chuck S · July 27th, 2005, 02:46 PM

Hello

You may modify your files however you wish to incorporate what you wish. We do not nor will we modify some other software that is not our own.

This is the beauty of php code that you can modify things to suit your needs. The way we change styles in reviewpost and template sets with Vbulletin integration works very well

Lionel · July 27th, 2005, 02:49 PM

Not a problem. I deleted my post. That's how much I get for being nice.

Chuck S · July 27th, 2005, 03:01 PM

Quote:

Sorry, will not try to help again

As I stated our application does not modify Vbulletin files. We code our application to work with Vbulletin as it is coded unhacked. It works very well with Vbulletin

If you hack your vbulletin install and reviewpost install something like this will always remain just that a hack. If you placed the same thing you posted here at Vbulletin.com they would give you the same response that you are welcome to hack your files as you see fit.

Lionel · July 27th, 2005, 03:07 PM

You could at least put out a decent product that does not necessitate one to dig in the code to fix bugs, such as that showcat.tml and so many others.

Chuck S · July 27th, 2005, 03:47 PM

Sorry you think that however just to point out since 2.91 was released in April there has only been like 4 reported bugs. I went back and counted them. I am not going to argue with you as you are entitled with your opinion just like anyone else.

Reviewpost 3.0 will be out shortly based on the new security typecast function currently in use in the other two products of ours and you may choose to upgrade or not.

Lionel · July 27th, 2005, 03:57 PM

Let me add one more bug. Reviews.php. reviews.php?product=XX
replace XX with non existant product number. Instead of an error message, the original template shows up. And if you try to add the review, you get an even uglier message. In order to fit your layout, one would have to work on a 100% table with a wide screen. So I changed the unecessary double columns, made use of css etc... I could have lived with that bug, if at least it was pulling my corrected template.

Chuck S · July 27th, 2005, 04:13 PM

Thanks and the correction would be to add this code in bold under the query in reviews.php.

Code:

Content visible to verified customers only.

Lionel · July 27th, 2005, 04:33 PM

Thank you. At least you fix the problems in a timely manner. That's a plus for you.
Unfortunately, that creates me tiny javascript inconvenience : the wysiwyg object was expected in that page. But that is livable with.