Just needing to find out what’s going on with my system. I installed my purchased extensions as well as some of your free ones and now have some issues with them. For example. When trying to login to the core the following appears for the twitter extension.
Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in /home/9189/domains/podcast-tuneup.com/html/ptcore/extensions/ext.lg_twitter.php on line 634
In EE I remove the extension and then can no longer move forward as it then provides and error stating that the extension is missing. I have been successful in replacing the extension and doing a refresh that will randomly allow access to the core. This extension seems to the problematic one in the group
Before I go mucking around in the DB I thought it best to post and get some guidance to the issue. This is very critical to moving forward as my developers cannot access the system to get work done as we’re under a tight deadline - please respond at your earliest convenience.
Michael, there’s nothwing wrong with posting here in the forums for assistance, but if you require assistance and/or a reply by Leevi in person, may I suggest to drop him an email instead?
As a quick bit of help on this one if you have disabled an extension (any extension) but then when you hit the template that has the extension tag code on it you will still get an error. You would need to take out the extension tag in the template for that template to not have problems again.
Don’t know if that is the case in this instance but have seen this a few times so thought it might be that.
If for instance you have something like :
{exp:twitter}
or whatever the code is then take that code out of your template and it should start working again. Just disabling and / or disabling the extension from the FTP site won’t make the errors disappear because if you still have the extension tag in the template then the system still tries to load that extension.
Thanks guys for the response. The issues isn’t with templates or where the developer placed tags as the extension was just installed and not used in any form as of yet. From the fact that it is installed and running it is now causing an error in the db and simply removing it will not change the issue. I should be able to remove it from the FTP as it has not been implemented in any way. Thus, the question is how to deal with this in the future once I clean the db of the error and move on. Maybe I won’t use the extension. I’ll check with Levi.
BTW - Levi states on his Web site to address issues with any of the extensions in the EE forums. However, I think I’ll send him a note!
Well, I have the latest Twitter extension (1.0.2) running on EE 1.6.3. and have PHP 4.4.8 running on A Media Temple Grid-Server. Maybe the PHP is the issue? Thought I checked the specs - I’ll check the CURL support on the service.
Hmmm could be an issue with the PHP version although I doubt it… I just uploaded what I have on my dev machine (runs fine) to my site. So grab the latest and see how you go.
The error relates to the end of the extension class… Maybe its because there is two class declarations in the same file?
Could someone with PHP5 install the extension and see if they get the same error?
Thanks Leevi for the quick response. Of course, you’re coming at me tomorrow I believe - Australia - correct?
I’ll have my Web admin have a thorough look at the issue and see what he can find. I’ll drop another post tomorrow late evening with what we’ve found. Thanks again -
We are using the LG TinyMCE extension. It works fine on one server. But a duplicate of that server (files and database) it doesn’t appear to be loading. The symptoms are:
* When viewing all custom fields for a field group, “WYSIWYG” is not listed on the fields that have been assigned that type (we’ve verified by editing the field itself that it is assigned correctly)
* When editing a page, the TinyMCE editor does not load. When viewing the source, it does not appear to be being called at all.
We’ve tried removing and reinstalling the extension, as well as removing and reinstalling tinymce to no avail. Any idear what’s going on?
I walked my happy hacking self all the way through leevi’s plugin. At the very end, there is a variable called $out which seems to hold all of the script sources required to call in tinyMCE. If I ‘echo’ that out, tinyMCE comes back! WOOHOO, sort of.
The problem now is that I’m not sure where it is returning that value. My guess is that it is returning the value to core.extensions.php, and that something inside there is eating the value. (Yes that is the technical term).
Perhaps one of the more experienced and or knowledgeable EE pEEple can jump in here and help us understand how core.extensions.php actually works.
When I copy the extension into the extension folder and goto Extension Management in order to activate it, I get the error
Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /homepages/27/d103776309/htdocs/schreibtisch/extensions/ext.lg_twitter.php on line 635
LG Twitter version 1.0.2
EE 1.6.4
PHP Version 4.4.8
libcurl/7.15.5
We are using the LG TinyMCE extension. It works fine on one server. But a duplicate of that server (files and database) it doesn’t appear to be loading. The symptoms are:
* When viewing all custom fields for a field group, “WYSIWYG” is not listed on the fields that have been assigned that type (we’ve verified by editing the field itself that it is assigned correctly)
* When editing a page, the TinyMCE editor does not load. When viewing the source, it does not appear to be being called at all.
We’ve tried removing and reinstalling the extension, as well as removing and reinstalling tinymce to no avail. Any idear what’s going on?
Thanks!
Which version of LG TinyMCE are you using? Also do you have any other extensions installed?
We ended up disabling the newsletter plugin and that seemed to fix the issues we were having with TinyMCE. Apparently they were both using the same hook? Sure would be nice if the EE folks could figure out a way to queue the requests for hooks to allow plugins to play more nicely with one another.
If you know of a way to make these to work together, do let us know. We likely have a need for the newsletter plugin in the future.
We ended up disabling the newsletter plugin and that seemed to fix the issues we were having with TinyMCE. Apparently they were both using the same hook? Sure would be nice if the EE folks could figure out a way to queue the requests for hooks to allow plugins to play more nicely with one another.
If you know of a way to make these to work together, do let us know. We likely have a need for the newsletter plugin in the future.
Thanks!
Extensions can both use the same hook without an issue if you are careful enough and follow the developer docs.
Do you have a link to the Newsletter extension? I’ll take a look to see if I can sopt an errors in LG TinyMCE and the Newsletter extension.
I’m running PHP 4. 
