Ah ok, so the warning shown could still be a warning from php.
But WP gives WPDB as the proper way to use direct database access and creation of own plugin tables etc. Now i’m wondering, how to use PDO in WP properly instead? Can’t find anything about this. I know how to setup a DB connection with PDO in PHP, but it seems to me there should be some sort of build in WP class like WPDB to use PDO.
I only got the warning after updating to WP 3.6. So guess this means the warning comes from WordPress ?
So, they have to fix the wpdb class?
Ah well, i see you’ll have to put out queries and stuff in the PDO way ( or mysqli ).
Anoying update , but probably necessary
Are you on PHP >5.5? mysql_connect and a bunch of the other mysql functions are deprecated in this version in favor of PDO. From the changelog:mysql: This extension is now deprecated, and deprecation warnings will be generated when connections are established to databases via mysql_connect(), mysql_pconnect(), or through implicit connection: use MySQLi or PDO_MySQL instead Dropped support for LOAD DATA LOCAL INFILE handlers when using libmysql. Known for stability problems Added support for SHA256 authentication available with MySQL 5.6.6+
Yeah i read that. But i was thinking – it’s not me using that function since i use the wpdb class AND i’m not even conntecting to a different database or something. So it’s WP itself using that function and then giving a warning?
i find i strange.. there are tons of plugins and themes using the wpdb in a proper way and they all get that warning?
I get this error while i only use the wpdb functions.
Anyone knows something about this?
I downloaded the google font JSON api file and wrote my own parses to let people select google fonts. This way the backend can just read it’s own font list without any api. This way you don’t have to put in a google api key inside the theme to load the list from the api every time.
But, the fonts loader is a better approach if you want to keep things always up to date though…
edit: or don’t you mean as an option for to chose in the backend? Don’t know if that could be done with fontsloader btw…
I’m using font awesome icons in one of my projects and when checking things out on a windows machine the icons look real ugly.
No matter if i look on firefox or explorer, seems like windows is the problem?
Anyone a hint for such thing?
I don’t like the whole mobile-first approach. It’s bad imo. When designing a nice website that needs to look unique and good on a normal screen, why let a mobile view hold you back.
Besides that, i liked the old look better. This one is SO ‘flat’, it’s looking ugly. But again, it’s a framework – so everyone should take from it what they can put to good use
For a couple of days i’ve been playing with backbone js and while trying to create things i put things in the console with console.log – to check if variables are updated etc.
Now today i’ve been bugging around with the problem that my whole model data and main JSON variable wasn’t updated properly.
When putting model data inside the console to check attributes and previousattributes it seemed the model wasn’t updating correctly – which is why i was debugging this ‘problem’ for like half a day
Now i found out, that the actual problem was Firebug showing wrong logs with inaccurate data. Since i desparately switched to chrome and checked the console there and turns out: everything was updating just fine! It was firebug not showing the correct data!
Anyone know something about this? Anyways, maybe people are hunting ‘problems’ because of this
Let me rephrase the issue and solution.
Issue: Let’s say you have a theme priced at 40$ and you decided to add more features to it to increase its value and after you did these updates, you found it is not fair to sell it at 40 and you should raise it to 45$ or 50$ and you already sold it to a couple hundred/thousands customer, the existing buyer got your work for free or in other words u lost about 5-10$ per existing sale.
Solution: Give the buyer option to pay the difference to get the new update, if he didn’t want to pay, he can access the old version of the theme, and to make this fair for both, the paid update shouldn’t have any fixes for existing code, it should only contain new features.This way, any author with a current theme can pay time and effort to make it more amazing for more 5$ from each buyer “this is not too much to pay to get a better theme if you love it”.
This can’t be done. You can’t raise the price of an existing item. Also, when uploaded an update, existing buyers can download it. So why would they pay you extra?
Anyway: Updates as they are now are fine. The ideas from the last posts even don’t have anything to do with what this thread is about.
And finaly: there is no issue, it was just an idea about recurring fees through envato for longer update life – which in turn: is a very bad idea. So the conclusion is: this thread should be closed