simco
Forum Replies Created
-
Forum: Plugins
In reply to: [Fast Secure Contact Form] After update to 3.1.8.1 the theme breaksQuick update, I did change the wp-config.php to add the following:
define(WP_MAX_MEMORY, ’64’);
Or whatever the tag was. Now it shows the 64 Mbyte and 30.55 usage respectively.
Forum: Plugins
In reply to: [Fast Secure Contact Form] After update to 3.1.8.1 the theme breaksThanks for your super quick response! I installed the plugin, here’s what it says:
PHP Version : 5.3.16 / 32Bit OS
Memory limit : 40 MByte
Memory usage : 30.55 MByteForum: Plugins
In reply to: [Fast Secure Contact Form] After update to 3.1.8.1 the theme breaksOn further notice, a problem has arisen regarding memory allocation when activating the plugin.
http://www.ncaied.org/contact-ncaied/
Please advise.
The actual error message, I had to disable the plugin and go with a stock form in the interim:
Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 262144 bytes) in /home/ncaiedor/public_html/wp-includes/wp-db.php on line 1223
Forum: Plugins
In reply to: [Fast Secure Contact Form] After update to 3.1.8.1 the theme breaksNever mind, found the problem! The site owner had slipped the page containing the form into the rotation of the main image slider on the home page and the shortcode for the form wasn’t able to parse in the truncated post summary in the slider display. Removed the page from the rotation and all is well.
Forum: Plugins
In reply to: [Awesome Flickr Gallery] Got Warning while activating pluginNo, using 3.3.4 which was the latest version available here. And, it doesn’t state an update is available.
Forum: Plugins
In reply to: [Awesome Flickr Gallery] Got Warning while activating pluginIt also had this warning as well:
The plugin generated 190 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.
Forum: Plugins
In reply to: [Awesome Flickr Gallery] Got Warning while activating pluginMe too, same issue.
Oh, sorry. I thought you wanted me to move that only as an experiment and not leave it that way so I moved the block of code back to its original location in the live acf file. Didn’t realize I was supposed to leave it.
I did notice everything is working and seems faster as well. So leaving that code block ahead of the document.ready, that’s not going to prohibit any of the functions of the plugin?
Emailed you the info.
Eliott, thanks for the response. I noticed this thread was referencing the page_template tag which is the same one my error message displays. Their theme is totally different than mine so it’s less possible that the theme is the issue. Here’s the thread link:
I’d appreciate some help simply because I know that the theme developers pretty much wipe their hands since it only occurs when we use this plugin. Therefore they blame the plugin. That’s how it’s commonly handled.
I understand the basics of what you’re explaining about how the error occurs. But trying to find the cause of it, i’m not a javascript expert. If it’s something that is more common than you may have though (like in the other thread) then it’s definitely something that would benefit you as well.
If you want to provide an email I can set up an account for you to take a look.
This is happening to me as well but only when i’m writing a ‘page’. If i’m writing a ‘post’ then the icons show fine. In ‘page’ mode, however, the icons appear in Visual mode but not in HTML mode. Also, the upload/insert media icon will not function.
Aside from that the plugin works fine and is displaying the custom fields exactly how I want. I just can’t use the editor to create a page and upload images. This is a problem because it’s a client site and it’s going to be hard to explain how to workaround the image problem.
Any help on a cure for this is greatly appreciated.
Unfortunately this is not resolved as reported. Exactly what I expected to happen is happening where the theme developers are pointing at you and vice versa. So, a week has gone by and nothing has happened. Hence my previous pessimistic posts based upon many experiences of this nature.
I see other forum posts regarding similar problems that point to the ‘page_template’ causing issues. Personally I feel there’s a conflict in the plugin when it comes to multiple selections of page templates. That’s the only connection I can see and is precisely mentioned in the error message.
I’d really like to get this resolved and it appears that it’s not only related to the themes i’m using (the other post reporting similar issues has an entirely different theme but also with various page templates to select from).
Need your help, Elliot. Thanks
I’m having a similar related issue. Do you have Chrome and the developer tools plugin? If so, pull up the javascript console and tell me what the error message is when you encounter that problem.
My issue is the admin area is broken due to a conflict somewhere with the ACF plugin and the error returned is specific to the page_template action. I’m curious what yours says.
I appreciate your candor and your honesty. AND, truly appreciate your quick responses. I think the frustration you read into my posts comes from the 15+ years of doing this where about 99% of the time the parties just point their fingers at each other instead of fixing the problem and guys like me get stuck in the middle. This, in turn, causes the clients on the designer’s side to get agitated when it appears nothing is happening. The normal result is simply finding another plugin OR starting over completely with a new theme which is not what I’d really like to do.
I’ve posted the issue in their support forums. It’s a membership site and i’ve been an active member for over 2 years so hopefully they’ll just say “Hey! We see that and *tweak tweak tweak* it’s fixed!”
Or, point me to where I can fix it myself. Either way works.
So, apologies if it came off as ‘rambo’ but I think I was bracing myself for what is usually the inevitable. I’ll keep you posted!
Thanks again for the quick responses!
Ok, so before I go back to them and tell them the problem is on their end, is what you’re saying they ‘should do’ is standard practice for WordPress themes? Or are they going to say they are doing it right and you’re doing it wrong. Hence the conflict with the plugin. Because what’s going to happen here is each party is going to point at each other. They’ll say that because it only conflicts with your plugin that it’s the plugin, not the theme. So, in order to have them ‘fix this’ they first need to be made aware that it is, specifically, their issue of non-compliance. See where I am with this? So, if what you’re describing is indeed an error on how they are executing their js then I have them by the balls. But, if not, then my balls are swinging in the wind. So can you clarify, please?