Jump to content

Community

Vroom

+Clients
  • Content Count

    163
  • Joined

  • Last visited

 Content Type 

Profiles

Downloads

IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Forums

Store

Everything posted by Vroom

  1. Can someone test whether they have this same problem. On my system I import email tickets from an email address. Someone sent an email there with an image attachment. When the cron ran to check the email and import it , the import failed. The cron attempted to repeat this every 1 minute. This resulted in the following: 1) In the system log, it added an error entry that included the insert sql query that contained the entire email including the 10mb image attachment. So each log entry was 10mb in size. Since it ran every 1 minute, in a few days this added 15 GB to my database until I got w
  2. It would be great if you made it a feature that guests could use the support system (at least create the ticket), as I would like to use the support system for sales inquiries (which is always new people who don't have an account) and it would be good to have the full features of using the different departments rather than the single generic contact us form. Or maybe allow the contact us form to have additional fields such as subject, ability to choose department, etc. I think many other people would also like to use the support desk in this manner. You could even
  3. It is like this: New install (4.0), adsense views = 12,000 per day. analytics views =12,000 per day. Old install (3.4), adsense views = 6,000 per day. analytics views = 12,000 per day. Both installs use the same URLs, topics, posts, etc. I can switch back and forth between both versions in a few seconds, so I have tested this over many days back and forth. As soon as I switch back to 3.4, the adsense views drop by 50%, but analytics views remain the same (over a 24 hour test period). And as soon as I switch to the clean 4.0 the adsense views go back up to 100% and analytics views remain the sa
  4. I am still looking into what is happening and how they are doing it, but probably they just searched for the copyright text in google or something like that, found an IPS board, and used an exploit. It's possible I was a day or two late on an upgrade around that time frame.
  5. I just noticed three of my IPB sites had been compromised at the end of May (around the 24th), so I would like to give you guys a warning to check in case you may have been affected as well. I noticed for the last couple months my adsense page views had dropped in half (exactly in half). At first I thought it was due to the google mobile updates. But after checking my analytics data I was still getting the same number of page views as before, only my adsense page views were down by half. After upgrading to 4.0 I saw my adsense page views instantly went back up to the regular 100%. Then I did a
  6. Is this still available in the admin cp? I cannot locate it.
  7. Thanks for the reply. I guess I will try my test queries on a backup database and see if I can get it.
  8. After upgrading I noticed that old posts converted every line break <br> into a <p> tag. I understand the use of the <p> tags, but a <br> is not the same thing and it wasn't used as a paragraph in old posts, why convert it to a paragraph. Why not leave it as a single line break? The problem is if you had posts like this (using line breaks): Little baby Oh so small One day you will be big and tall I watch you while you laugh and play My love for you grows everyday I tell you this with my whole heart I love you just the way you are Now it looks like this: Little baby O
  9. I find the html editor to be very difficult to use, as it creates the html in a single run on line which makes it almost impossible to read comfortably. The old system of BBCode was so much easier and cleaner. Do many people really need the ability to write full html with javascripts and divs in a message post? Maybe one tenth of a percent of users could even utilize that. BBCode seems to be the safe and easy way to grant a basic source editor to all users. But having said that I don't think it will ever come back. Seeing the new editor my gut feeling is it is gone for ever.
  10. The background processes were still running. I had already activated the cron setting. It looks like the crons were what killed my server. I will test it without the crons running for a day. So far load is looking very normal now that the cron was disabled. But I will have to get the background processes completed slowly without over burdening the server, maybe with a bigger time gap, or maybe manually.
  11. Disabling the one minute cron dropped the load down, though still slightly higher than before. I will watch it today and see if the apache problems come back or not.
  12. This is feedback on my experience upgrading to 4.0. After upgrading, my apache is dying at least 5 times a day, causing all sites on the server to be unreachable. I never had this even once in the last 5 years. Forum has 2 million posts with 30,000 page views per day, which is not that much for a very powerful dedicated server with only a few other less active sites on it.
  13. I have three vbulletin licenses (from when it was $285 each). Maybe somewhere I can trade them for a Winrar license.
  14. I had upgraded to IPB from vbulletin a couple years ago when it was clear vbulletin was a sinking ship. I had used vbulletin for probably 10 years. When I decided to finally change over, I could see vbulletin was going down hill and was on the verge of disappearing. So I took the hard decision to abandon ship and find the best forum software available in the present times. At that time there was a lot of complaints about the vbulletin 5.0 which was supposed to come out "soon", and from the samples it was clear it was a piece of junk. So out of curiosity, yesterday I thought let me go check the
  15. FIxed it, I had to also uninstall the hooks it created, not just the application.
  16. I just uninstalled it and deleted the files, and now my forum is broken giving the following message: Fatal error: Uncaught exception 'Exception' with message 'greenseo is not an object' in /home/XYZ/public_html/XYZ/admin/sources/base/ipsRegistry.php:1115 Stack trace: #0 /home/XYZ/public_html/XYZ/admin/sources/base/ipsRegistry.php(1213): ipsRegistry::getClass('greenseo') #1 /home/XYZ/public_html/XYZ/hooks/greenSeoPublicOutput_35ae8eda84456ed9916173a069000645.php(49): ipsRegistry->__get('greenseo') #2 /home/XYZ/public_html/XYZ/admin/sources/classes/output/publicOutput.php(2289): greenSe
  17. I'm dissapointed in this, as there is no mention in the marketplace listing that the converter does not retain the same topic ID when importing threads. I was converting from a VBSeo site and thought this would help me from losing my google rankings by keeping the same URLs for the old threads, but it doesnt do this at all since the thread ID numbers are different in IPB and your old forum. Thus this software is useless, and I wasted $65 for nothing. I believed it when you wrote "With this modification you can switch your vBulletin + vBSEO combination to IPB with NO indexed thread or forum U
×
×
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy