Ya, i havent had time to get it updated. having work ftw .
I noticed a slight issue before i do the next update and i want to get the VBSEO thing figured out.
Right now when you enter an item and make a new post, all is well. However if you go to Edit that post later, the item name ([item]Belt of Blasting[/item] ) has changed to the itemid instead ( [item]42423[/item] )
While the item mouseover itself is not effected in any way, it's something that isnt needed if you're trying to update say, a list of loot received in raids.
Saturday morning (i swear!) , i'm going to update it so that it changes [item]Belt of Blasting[/item] to [item=12312]Belt of Blasting[/item] . This way you won't run into an issue in the event you want to link a Warglaive (or any item that has duplicate name)
i think i narrowed it down, it seems to be a vbSEO confliction
Both were taken from the same thread as i noticed it wasnt an issue on my dev server which does not have vbseo enabled.
VBSeo uses supplied methods of adding the base tag to the template cache. I'll ask on the vbseo forums if its possible to get around the issue.
Quote:
Originally Posted by CremeEgg
Sounds ace, I noticed that it already works with http links to spells, but yeah would be great to see it with spell tags too.
Don't forget to add it to the editor
Added the item link to the editor (type a name, highlight it and hit the wowhead icon). Support for spells won't be available at this time because wowhead doesnt supply a XML feed for spells, just items. I may build a database of spells w/spell IDs though, but it wont happen right now.
Quote:
Originally Posted by Evolution06
Did you have time to do the update? Just wondering I mean it seems to work fine but I hate uploading stuff when it gives me a error.
I removed the part that i think was giving the error. it was install code that removed plugin that i added via database, which isnt really needed.
It's to bad that it couldnt give me more information about whats going on here but i think i have an idea.
Expect a minor update tonight.
I don't know if you got that error fixed but unexpected T_ENCAPSED_AND_WHITESPACE, expecting T_STRING or T_VARIABLE or T_NUM_STRING simply means you have an unclosed string somewhere.
I don't know if you got that error fixed but unexpected T_ENCAPSED_AND_WHITESPACE, expecting T_STRING or T_VARIABLE or T_NUM_STRING simply means you have an unclosed string somewhere.
Ya, but the question was where. While the issue was easy to find, it isnt obvious as to what module or hook the error is happening in. you have to review source code to find that the eval call thats throwing the error is part of the plugin install routines, etc.
Of course, there isnt anything you can do about it in vbulletin. I don't think php has (or can) added that type of error handeling to where it will tell you the info you need.